dev-story

Automate game story implementation by reading story files, validating dependencies, routing to the correct programmer, and generating code and tests. This Skill requires proper context files, story structure, and manifest adherence to process the implementation automatically.

Automated story routing works by directing the story file to the appropriate programmer agent based on the story's layer, type, and system name. It ensures the correct code generation logic is applied for each specific game system requirement.

Context files needed for programming automation include GDD requirements, ADR guidelines, and control manifest. Proper story structure and manifest adherence are also required to validate dependencies before code implementation begins.

Yes, you can generate test files automatically when implementing game stories. The Skill generates source code and test files according to ADR guidelines and manifest rules after validating that all required dependencies are in place.

Dependency validation fails during story implementation when required components are not in place or context files lack proper manifest adherence. The Skill checks dependencies to ensure all necessary GDD requirements and ADR guidelines exist before routing to a programmer.

The best way to structure game story files for automated code generation is to ensure proper story structure and manifest adherence. Include necessary context like GDD requirements and ADR guidelines so the routing system can identify the correct layer and system name.