What problem does it solve? Turning a written story or task document into working, tested code requires disciplined sequencing: validating the document is ready, checking for conflicting existing implementations, writing tests, and recording what was built. This Skill enforces that workflow so implementation stays aligned with requirements and fully documented. ## Core Features & Use Cases - Document-driven implementation: Detects story, task, or epic files by naming pattern, validates status (Draft, Ready for Development, In Progress), and blocks development of epics by routing to story or task creation first. - Risk and alignment gates: Flags high-risk stories (auth, payments, crypto) and offers to run QA planning first; analyzes existing code against the document and resolves misalignment with the user before writing code. - Test-gated task completion: Runs lint and test checkpoints per task, captures failures to log files with triage, applies a three-strikes escalation rule, and only checks off tasks when all tests pass. - Use Case: Run it on story.178.8.example-feature.md and the agent validates the story, checks risk level, aligns with any existing code, implements each task with co-located tests, and maintains a complete Dev Agent Record with file lists and change logs. ## Quick Start Ask the agent to develop the story file at stories/story.178.8.example-feature/story.178.8.example-feature.md and follow its guided implementation workflow.