What problem does it solve? Enforcing strict test-driven development across a full feature implementation requires coordinating many specialized steps—planning, test design, adversarial spec review, implementation, coverage auditing, mutation testing, and final review—in the right order with the right test lanes at each stage. This Skill removes the guesswork by defining that orchestration explicitly, including mandatory stop conditions when gates fail. ## Core Features & Use Cases - Seven-stage subagent orchestration: Runs tdd-planner, tdd-test-designer, tdd-spec-adversary, tdd-implementer, tdd-coverage-auditor, tdd-mutation-auditor, and tdd-reviewer in a defined sequence with feedback loops. - Lane-aware execution: Runs only fast taskCompleted lanes in the inner implementation loop, deferring slower commit and push lanes to explicit gate checks at the end. - Mandatory stop conditions: Halts on any gate failure, treats zero-discovered-test lanes as failures, and never commits or pushes until gates are green. - Use Case: When asked to implement a new feature with strict TDD, the workflow produces a test matrix with specification levels, attacks it adversarially before any code exists, implements in small red-receipt batches, then audits coverage and mutation strength before final review. ## Quick Start Ask the assistant to implement a new feature using the strict TDD workflow with full gate enforcement.
