What problem does it solve?
Dev story implementation often suffers from context drift, missing design requirements, and incorrect routing to specialist engineers, leading to rework and delayed delivery. This Skill eliminates those gaps by automatically loading all required context, validating dependencies, and enforcing design guardrails before any code is written.
Core Features & Use Cases
- Full Context Loading: Automatically gathers the story file, GDD requirement (from the TR registry), governing ADR, control manifest, and engine technical preferences to ensure no design details are missed.
- Specialist Routing: Routes implementation to the correct programmer and engine specialist based on the story's layer, type, and tech stack (e.g., Babylon.js, Godot, Unity) to get expert-level code.
- Guardrail Enforcement: Validates dependencies, checks control manifest rules, enforces scope boundaries, and requires automated tests for logic and integration stories to ensure acceptance criteria are met.
- Use Case: For a 90s F1 racing game built with Babylon.js, use this Skill to implement a story for car physics: it will pull the relevant GDD requirement, ADR for physics implementation, route to the gameplay and Babylon.js physics specialists, and deliver tested code that meets all acceptance criteria.
Quick Start
Invoke the dev-story skill with the path to a ready dev story to automatically load all required context, route to the correct specialist programmers, and deliver tested code that meets every acceptance criterion.
