dev-story

Automated story implementation resolves sprint stories by loading full project context, routing to the correct programmer, and generating working code with tests. It converts planning artifacts into ready-to-review code by enforcing ADR guidelines and manifest rules.

ADR-driven code generation enforces guidelines by loading architectural decision records and control manifests during implementation. It applies these rules to controlled changes in src/ and tests/, ensuring the generated code complies with established project constraints.

Converting a sprint story into working code requires loading the story file and assembling contextual data like GDD requirements. The process routes work to the appropriate engine specialist, driving phase-driven workflow from readiness through test generation and code review.

Automatic test file generation occurs during story implementation by validating acceptance criteria and writing test artifacts. The process drives code and test implementation across multiple phases, returning a ready-to-review implementation with accompanying tests.

Programmer routing integrates engine specialists by determining the correct agent for the specific story context. It reads the full story file, assembles contextual data including GDD requirements, and routes work to the appropriate programmer for end-to-end delivery.

A control manifest is needed for automated coding workflows when a sprint story requires converting planning artifacts into code. It enforces controlled changes to src/ and tests/, ensuring the implementation adheres to manifest rules and ADR-driven guidelines.