dev-story

Automate story-to-code implementation by reading a story file and routing it to the appropriate programmer agent based on layer and type. The workflow assembles the full contextual stack, including GDD requirements and ADR guidelines, to generate production-grade code and tests.

Writing code from a story file involves assembling the story context, GDD requirements, ADR guidelines, and control manifest. The AI agent then enforces ADR-guided guidelines to implement code, writes tests, and validates the output against each acceptance criterion.

An AI agent enforces architecture decisions by applying ADR-guided guidelines during code generation. It reads the control manifest and routes the implementation to the correct programmer agent, ensuring the generated code and tests align with predefined system goals.

Yes, you can route story implementation tasks to specific programmer agents. The orchestration routes the story file to the appropriate expert programmer agent based on the system layer, type, and engine goals to implement the required code.

Yes, you need a story readiness check before starting end-to-end code implementation. The core implementation workflow is designed to run after story readiness validation and before code review, ensuring all contextual prerequisites are met.

A limitation of using a programmer agent for story implementation is that it requires a fully assembled contextual stack, including GDD, ADR, and control manifest files. Without these predefined inputs, the agent cannot accurately route or validate acceptance criteria.