What problem does it solve?
Dev-story removes the friction between story planning and working code by turning a fully specified sprint story into an implementation plus the required automated test, with guardrails that keep you aligned to the controlling ADR, TR requirements, and layer rules.
Core Features & Use Cases
- Full context assembly for programmers: Reads the story, TR registry requirement text, governing ADR implementation guidelines, and control manifest rules for the story’s layer, so implementation follows the source of truth rather than stale narrative.
- Dependency and readiness validation: Validates that story dependencies exist and are in an acceptable status before implementation, and blocks progress when TR/ADR essentials are missing.
- Automated test creation and coverage: Enforces creation of the test file required by Logic/Integration stories and maps acceptance criteria to test functions.
- Session-state and sprint bookkeeping: Marks sprint status as in-progress and updates the story’s Last Updated field to support staleness detection.
- Use Case: When a hatchery sprint story is marked ready, run dev-story to implement the feature and its tests, then proceed to code review and story closure.
Quick Start
Use dev-story with a story path like 'production/epics/hatchery/story-005-dragon-unlock-duplicate-xp-and-shiny-upgrade.md' to implement that story with the correct context and required tests.