dev-story

To turn story files into code and tests, load TR registry requirements and ADR guidelines, then route the story context to the appropriate programmer agent for implementation. This workflow ensures test evidence is created at the path specified in the story header before closure.

Story-driven development for test automation is a process that converts planning artifacts with acceptance criteria into working implementations. It orchestrates context loading, agent routing, and mandatory test coverage to eliminate the gap between planning and functional code.

To enforce ADR guidelines during code generation, apply control-manifest rules within the story layer and verify required architecture files before spawning implementation agents. This validation-first workflow blocks execution safely if dependencies or manifest versions are incompatible.

Yes, you can generate tests for Logic and Integration stories automatically. The workflow mandates the creation of test evidence at the path specified in the story header, ensuring acceptance criteria are fully covered before the story implementation is closed.

Yes, agent orchestration routes stories based on engine risk and story context. The workflow applies control-manifest rules to route work to the appropriate programmer and optional engine specialists across Logic, Integration, Visual, and Config story types.

Story-to-implementation orchestration is limited by its dependency on end-to-end context verification and manifest version compatibility. If required architecture files are missing or story dependencies fail validation, the workflow safely blocks implementation from proceeding.