dev-story

To turn story specs into working code, this Skill reads your story file, loads the required TR registry and governing ADR, then routes specialist programmer agents to implement code and tests that satisfy acceptance criteria.

The best way to implement sprint stories with architecture validation is using a skill that enforces TR registry and governing ADR presence, loads control manifest rules per layer, and blocks implementation when required architecture assets are missing.

Agent routing for different story types works by automatically selecting specialist programmer agents based on story layer and type, such as UI, Visual/Feel, or AI/pathfinding, while skipping agent spawning entirely for Config/Data stories.

Yes, you need architecture assets like ADRs before starting story implementation. The Skill validates story readiness and blocks implementation when required architecture assets or dependent story completions are missing.

Story implementation requires test evidence before completion to ensure logic and integration layers are fully validated. The Skill mandates test evidence for these specific story types to enforce quality and readiness across sprint workflows.

Yes, you can use this for game engine integration and config data stories. The Skill handles logic, integration, UI, visual/feel, and config/data story types with engine-aware specialist routing, though config/data stories skip programmer agent spawning.