What problem does it solve?
It solves the problem of turning a structured “story spec” into a correctly implemented, fully tested change set that meets acceptance criteria and is ready for review.
Core Features & Use Cases
- Story-driven implementation: Executes tasks strictly in the order defined by the story’s Tasks/Subtasks and gates progress on completion and passing tests.
- Sprint-aware workflow: Discovers the next “ready-for-dev” story from sprint-status.yaml (when available) or from story files (when not).
- Review-continuation support: Resumes after code review by prioritizing unresolved [AI-Review] follow-ups from the story and review sections.
- Traceable, auditable outputs: Updates only permitted story sections (checkboxes, Dev Agent Record, File List, Change Log, Status) and summarizes actual changes and tests for review readiness.
- Quality and DoD validation: Enforces a definition-of-done checklist, including regression checks and documentation/tracking completeness.
Quick Start
Use the command “dev this story <full-path-to-story-file>.md” to implement the story described by the spec, run validations, and mark it ready for review.