implement

Automate backlog story implementation by coordinating sprint-dev with flags like --sprint and --stories to execute stories phase-by-phase. The skill manages state via STATE.md checkpoints and logs progress to the activity feed for predictable delivery.

Automated sprint checkpointing tracks implementation progress by persisting state transitions to a STATE.md file at every phase. This ensures resumable execution and provides an auditable record of story-level completion during the sprint.

Validate a sprint before implementation by running pre-flight checks for the sprint registry, story existence, and active sprint-dev sessions. The skill also enforces a clean build baseline to ensure a stable starting point for execution.

You can resume sprint implementation because the skill persists state via STATE.md checkpoints after each phase. Running the skill again with the appropriate --sprint flag reads the checkpoint to continue story execution from the last valid state.

Sprint implementation works without external dependencies, relying instead on internal state management via STATE.md and event logging to the activity feed. It orchestrates the existing sprint-dev workflow rather than requiring third-party libraries.

A clean build baseline is required to prevent compounding errors during automated story implementation. Pre-flight validation enforces this baseline so that any failures detected during sprint execution are attributable to the current story, not pre-existing code issues.