dev-story

Story implementation with tests is achieved by loading the story file, pulling the required GDD requirement and governing ADR, then routing the work to specialist agents to write scoped source code and test evidence in the project's src/ and tests/ locations.

Architecture validation works by enforcing dependency checks and requiring a TR registry and governing ADR presence before safe execution, ensuring the story implementation aligns with the control manifest rules for the specified layer.

Yes, you can generate tests for UI and Visual workflows, but test evidence is a strict hard requirement specifically for Logic and Integration stories, where each acceptance criterion must be covered by a test file.

The best way to prevent spaghetti implementation is to use story-driven implementation that reads a story file, loads the correct architecture context, and performs acceptance criteria verification alongside the code change.

Yes, you need a TR registry and governing ADR presence for safe execution, and the system can optionally enforce manifest version alignment to ensure the generated code matches the defined architecture.

Game engine routing matters because it selects the appropriate programmer agent based on the story layer, type, and engine context, executing the implementation to completion without incorrect cross-layer dependencies.