implement-stories

Automating Scrum story implementation involves classifying stories by acceptance criteria and routing them to matching code generators. This skill handles dispatch automatically, topologically sorting dependencies to process batches in correct order.

Managing cross-story dependencies during batch code generation requires topological sorting based on 'Depends On' relationships. This ensures correct processing order and stops execution on critical failures to prevent cascading errors across the sprint.

Enforcing acceptance criteria validation inline requires running validation gates immediately after each code generation step. This approach surfaces handbook and criteria issues instantly, preventing deferred end-of-batch review errors.

Batch-implementing an epic of ingestion and DAG stories is fully supported. The skill processes entire epics or sprints in one run, automatically handling dispatch, inline validation, and logging without manual tracking.

Automated story implementation integrates directly with existing create and update generator skills. It routes classified stories to these generators based on acceptance criteria content, ensuring a deterministic and auditable pipeline.

You should avoid automated story implementation pipelines when stories lack clear acceptance criteria or defined dependency relationships. Without these inputs, the topological sorting and intelligent dispatch mechanisms cannot function correctly.