Getting started with Agentic — workflow, commands, and how the agent team works together.
The Test Advisory output format used by all tester specialists (tester-coverage, tester-artisan, tester-architect) and understood by the Lead for synthesis. Defines sections, severity tags, dual verdict, and the specification template. Loaded whenever a task produces or consumes a Test Advisory.
Core testing principles shared across the tester specialists (tester-coverage, tester-artisan, tester-architect) and the developer agent. Defines what a good test is in this codebase. Loaded whenever a task involves writing, auditing, or specifying tests.
Shared review craft for all reviewer specialists — confidence scoring, verdict rules, output format, and the signal-over-noise discipline. Applied by every reviewer agent regardless of lens.
Code conventions and style convictions. Applied when writing, reviewing, or analyzing code. These are non-negotiable standards, not preferences.
Provides git workflow conventions including Conventional Commits, branch naming, and PR descriptions. Applied when committing, branching, or creating pull requests.
Identifies code quality anti-patterns and provides best practices. Applied when analyzing code smells, architecture decisions, complexity, or technical debt.
Identifies security vulnerabilities and provides secure coding patterns. Applied when reviewing code for injection, authentication, authorization, and data exposure risks.