dev-story

Implementation workflow automation reads your story file to load context like ADR guidelines and TR registry data, routing tasks to appropriate programmer agents while coordinating tests and evidence collection across the lifecycle.

Automating code execution from a story file requires routing to the correct programmer agent based on the story's layer and type, verifying acceptance criteria, and surfacing blockers or required user input before execution begins.

Yes, the implementation workflow explicitly follows ADR guidance, TR registry data, and manifest rules to drive decisions, ensuring that architectural constraints are respected and blockers are surfaced before code execution.

Routing a story to the correct programmer agent is handled automatically based on the story's layer, type, and system, ensuring the right expertise is engaged for your specific implementation requirements and context.

Yes, you can coordinate implementation steps, tests, and evidence artifacts across the workflow from story readiness through dev-story and code-review to story-done, respecting dependencies and surfacing questions before execution.

The workflow stops to ask for user input because it respects dependencies and blockers, proactively surfacing questions or required decisions before proceeding to the code execution phase.