dev-story

Automated game story implementation translates structured studio specifications into working source code and automated tests. It validates traceability registries, enforces architecture decisions, and routes tasks to correct programmer agents to ensure changes align with engine conventions.

Requirements traceability during code generation uses a TR registry as the source of truth. The system validates this registry and governing architecture decision records before implementation, blocking execution if they are missing, to ensure end-to-end story requirements are tracked.

Yes, you can use it for Unity game development sprint stories. It automatically routes Logic and Integration stories to Unity programmer agents based on the specified story layer and engine risk, ensuring generated code adheres to engine-specific conventions.

When manifest version alignment fails during story-driven development, the implementation process pauses. It requires an explicit user decision to proceed despite the mismatch, ensuring you maintain control over architecture enforcement and prevent unintended dependency conflicts.

Acceptance criteria test coverage for Logic sprint stories is ensured by writing an automated test file at the story's Test Evidence path. The system enforces this rule, validates each acceptance criterion, and summarizes coverage for your review loop.