What problem does it solve? Executing an approved development plan requires coordinating implementers, testers, reviewers, and fixers across multiple rounds with human approval gates. This Skill automates that orchestration as a state machine, checkpointing every stage to disk so work survives session interruptions and never loses track of findings or decisions. ## Core Features & Use Cases - Mode-based execution: Choose light (default, two review axes, no mutation testing), full (four review axes plus mutation testing), or noreview (no reviewers) at preflight; the mode is frozen for the entire run. - State machine with human gates: Drives IMPLEMENTING → TESTING → REVIEWING → FIXING rounds with exactly two human gates (triage of findings and READY_TO_COMMIT), plus escalation on budget exhaustion, blocked stages, or repeated failures. - Crash-safe checkpointing: Appends every stage result to a LOOP file after each return, so a session can resume from disk artifacts alone without relying on conversation memory. - Use Case: After approving a plan written by plan-dev, run the loop in light mode to have an implementer write the code, a tester verify it against the Acceptance Contract, and two reviewers check maintainability, stopping for your decision on any findings before reporting READY_TO_COMMIT. ## Quick Start Run the approved plan at docs/agents/dev/PLAN.md through the dev loop in light mode and stop at ready to commit.
