dev-story

To implement sprint stories with ADR compliance, load the TR registry, governing ADR, and control manifest before coding to ensure rules are followed. The dev-story Skill reads your story file, routes to the correct specialist agent, writes the code, and generates the mandated test evidence.

The best way to ensure code follows architecture rules across Logic, Integration, and UI layers is to validate dependencies and check manifest version alignment during story implementation. This approach enforces guardrails by blocking progress when required architecture inputs are missing.

Agent routing for game engine tasks selects the primary programmer based on story layer and type, then spawns the appropriate engine specialist when engine risk is high. This engine-aware routing ensures code changes align with specific engine preferences and constraints.

Yes, you need a control manifest and TR registry to generate tests for Logic stories. The implementation requires loading these architecture files beforehand to enforce guardrails, validate dependencies, and ensure the mandated test evidence is created alongside the source code.

You can use this approach for Config and Data story workflows without writing tests, as test-enforced completion applies specifically to Logic and Integration stories. The implementation still validates dependencies and checks manifest version alignment for all story types.

Story implementation fails when architecture files are missing because built-in guardrails block execution to prevent code drift and rework. Validating the presence of the TR registry, governing ADR, and control manifest ensures code changes comply with required design context.