dev-story

Automating story implementation in game development requires reading story files, validating them against architectural requirements, routing to specialists, implementing code, and testing. This Skill automates that complete workflow.

Validating game feature stories against ADRs involves parsing the story file and checking its implementation requirements against the project's Architecture Decision Records and TR registry. This ensures the proposed feature aligns with existing technical constraints.

Integrating code review into game development workflow automation requires a system to route implemented code back for quality validation. This Skill triggers code review automatically after reading, validating, and implementing the story file.

Story implementation automation requires access to project files, ADRs, and the TR registry to function correctly. It eliminates manual tracking by automatically reading and processing these inputs to route tasks to the correct specialists.

The primary limitation is its strict dependency on existing project infrastructure; it requires accessible ADRs, a TR registry, and properly formatted story files to route and implement code, meaning it cannot operate in projects lacking these architectural documents.