dev-story

Story implementation is coordinated by loading full context from story files and routing to the correct programmer agent based on layer, type, and ADR rules. This ensures code and tests align with manifest constraints before producing a reviewable package.

To align implementations with ADR and manifest rules, load the complete context including GDD requirements, TR registry, and control manifest before coding. This validates dependencies and surfaces blockers or deviations early in the process.

Test file generation is enforced during story implementation by applying constraints to Logic, Integration, and applicable UI stories. The routing mechanism ensures the programmer agent writes tests alongside code for a complete, ready-to-review package.

AI agent orchestration works with control manifests and TR registries by loading them as context constraints. It validates manifest alignment and enforces TR registry rules before coding begins, ensuring traceable changes within established boundaries.

To start story implementation, run the command with a valid story path. This triggers context loading, validates dependencies, routes to the correct programmer agent, and produces a complete implementation package with documentation.

Engine specialists are spawned during story implementation for post-cutoff risks identified after routing to the primary programmer agent. This handles specialized layer requirements while maintaining ADR and manifest compliance.