dev-story

Automating story-to-code implementation in Godot uses an orchestrator to read a story file and route tasks to specialized AI agents. These agents execute phase-based code generation, write tests, and validate artifacts against an ADR and manifest.

Phase-based routing for AI-driven game development directs specific story layers to specialized programmer agents. This enforces structured implementation by validating required artifacts and architectural rules before generating code and tests.

Validating architectural rules during AI code generation requires assembling full project context. The workflow loads an Architecture Decision Record, a Technical Requirement registry, and a control manifest to ensure alignment before routing implementation.

This story-to-code workflow supports testing and validation orchestration. It coordinates specialized agents to produce test files alongside code implementations and generates an implementation summary and session memory update.

To trigger an end-to-end implementation workflow, you need to provide a story path. The orchestrator then assembles the required GDD requirements, ADR guidelines, and control manifest to drive automated code generation.

Orchestrating AI agents for Godot game development is limited to projects that provide required artifacts. You must supply a story file, ADR guidelines, a TR registry, and a manifest; without these, phase-based routing and validation cannot execute.