brief-writerExtracts a task brief from an implementation plan plus the current code (interfaces, file paths, constraints, exact values). Reads and summarizes; makes no design decisions. Use to prepare the single source of requirements an implementer will work from.
complex-implementerImplements one plan task that the plan marks as complex (`**Role:** roles:complex-implementer`): multi-system changes, migrations of live state, or work where a mistake is costly. Works from a brief with strict TDD (write the failing test, run it, implement, run it green), verifies with focused test
final-adversarial-reviewerSingle high-value adversarial review of a whole branch before merge: tries to break the implementation against the spec, hunts correctness and security defects across task boundaries, triages deferred and parked findings, and states what must be fixed before merge. Use once per branch, after all tas
hunterHunts for defects in one diff package for one category (correctness, security, spec-drift or state) and writes its candidates to a single file. Finds and reports; never fixes, never grades severity. Use for the cheap, wide first pass of a review that a stronger reviewer then confirms or refutes.
phase-orchestratorRuns one phase of an implementation plan by following methodology:executing-plans for that phase only: dispatches the role agents task by task, runs the task scripts and reviews, and returns a short summary to the controller. Never edits product code itself. Use once per phase, in place of the contr
review-fixerResolves review findings on a task branch: fixes what is real with the smallest correct change, and refutes with evidence what is wrong instead of implementing it blindly. Re-runs covering tests, commits, appends a fix report. Use for fix rounds after a task review.
safety-reviewerMechanical checklist review of one task diff: commit message and trailers, secrets or credentials in the diff, forbidden paths or directories touched, file placement versus the plan's file structure, lint/typecheck evidence present, canary rules from the project's global constraints. Use for the che
spec-reviewerJudgment review of one task diff against its brief and spec: missing, extra or misunderstood requirements, and test honesty (tests assert real behavior, RED/GREEN evidence is genuine, edge cases covered). Traces code paths and branches. Use for the spec-compliance and quality gate of each task.
tdd-implementerImplements one plan task from a brief with strict TDD (write the failing test, run it, implement, run it green), verifies with focused tests and the typecheck/lint scoped to the touched files (never the full suite), commits, self-reviews and writes a report. Use for every implementation task in plan