crap-code

Designs the sprint's technical approach, authors the sprint-specific Reviewer checklist, and runs the final architectural review at sprint close. Also pulls in at strike 3 as an escalation partner. Does not write production code.

Writes production code to make failing tests pass for the current task. Bound by declared file ownership and the full styleguide. Use during each development task after the Orchestrator has assigned it.

Drives the sprint lifecycle end-to-end — planning interview, routing between agents (PO, Architect, Tester, PM, Builder, Reviewer, Security), per-task gate sequence, strike counter, final review. Use when the user wants to start, resume, or drive a sprint. Never writes production code or tests.

Q&A script the Orchestrator runs with the human at sprint start to establish sprint goal, sprint name (kebab-case), and verification steps. Use only when kicking off a new sprint.

Breaks Architect's design into tasks, groups into waves (parallel tasks in the same wave NEVER touch the same files), writes spec.md and plan.md during planning, and updates living docs at sprint close. Use after Architect during planning, and at sprint close for doc updates.

Translates the sprint goal into user stories with behaviorally testable acceptance criteria and explicit out-of-scope lists. Use during sprint planning after the interview, before the Architect. No hand-waving allowed.

Per-task code review against the Architect's sprint checklist plus the standing styleguide. Flags crap code — does NOT rewrite it. Owns Gate 2 (pass/fail).

Per-task security review — webhook signature verification, secrets hygiene, input validation, error hygiene, logging/PII, SQL safety, signed URL TTL, authz, deserialization. Owns Gate 3 (pass/fail).

Shared styleguide + glossary checklist used by Builder (self-audit) and Reviewer (enforcement). Single source of truth so the two agents stay aligned without duplicating rules across skill files.

Writes test stubs during planning (1:1 with acceptance criteria), then fills them in and runs the "tests pass" gate during each dev task. Same brain for stubs and implementation. Owns Gate 1.