What problem does it solve? It turns a Ready story file into disciplined implementation work by enforcing the Definition of Ready before coding, tracking acceptance criteria as they are completed, and capturing every decision and defect as versioned markdown artefacts instead of losing them in chat history. ## Core Features & Use Cases - DoR Gate Enforcement: Verifies the Definition of Ready checklist and refuses to start work on stories that are not actually ready. - AC-Driven Implementation: Works acceptance criteria one at a time, ticking each checkbox in the same edit as the code change, and wires the paired testplan's test cases. - Decision and Defect Capture: Files ADRs for non-obvious decisions and BUGs for observed defects on the spot, with a spec-error exception that routes wrong acceptance criteria to an ADR instead. - Use Case: A solo developer pulls STORY-03.1.02 from the stories folder; the skill flips its status to in-progress, implements each AC, records two ADRs and one BUG, and stops at in-review ready for the testplan run. ## Quick Start Ask the assistant to start work on a specific Ready story file, for example by saying to execute STORY-03.1.02 from the stories folder.