dev-story

Automating game feature implementation requires loading full context like GDD requirements, ADRs, and control manifests from a story file. The system then generates source files in src/ and corresponding tests in tests/ while recording changes in the session state.

Story-driven code generation is a workflow where stories define requirements, ADRs, and test criteria for code implementation. It applies to game development by turning story files directly into working source code and tests without manual context gathering.

Generating source code and tests from GDD requirements involves loading the full design context and routing to appropriate programmer and engine specialist agents. These agents generate source files in src/ and create corresponding tests in tests/.

Yes, architecture decision records (ADRs) are required to implement game features using this workflow. The system loads ADRs along with GDD requirements, control manifests, and engine preferences to ensure the generated code aligns with architectural decisions.

Dynamic routing for code generation works by determining and spawning appropriate programmer and engine specialist agents based on the story layer, type, and risk. This ensures the correct specialists handle each aspect of the implementation.

When story dependencies or manifest versions don't match, the system validates dependencies, manifest versions, and required files before proceeding. It then prompts the user when mismatches occur to resolve issues before code generation begins.