What problem does it solve?
It solves the problem of building and validating software features in a deterministic, enterprise-grade way, even when tools and execution context vary.
Core Features & Use Cases
- Spec-isolated TDD per milestone: implements each milestone with strict context isolation so the test authoring and code implementation don’t contaminate each other’s inputs.
- Contract-mapped status reporting: runs tests mechanically and produces status reports that map failures to specific tech.yaml contract IDs for precise fault localization.
- Quality gates and QP certification: enforces build, lint, unit tests, type checks, coverage, and QP certification before any judge review proceeds.
- Self-repair loop with arbiter escalation: retries fixes up to three cycles and escalates to judge-as-arbiter when the same contract fails twice, deciding whether the implementation, the test, or the spec is at fault.
- Milestone-based execution: validates each milestone before moving to the next, preventing dependency issues from leaking into later work.
Quick Start
Use the implement skill to build a locked feature milestone by running: implement --milestone T-001.
