sprint-plan

A sprint plan consolidates backlog items, milestone targets, and previous sprint velocity to assemble tasks, estimates, and capacity. It produces a markdown sprint document and a machine-readable production/sprint-status.yaml after passing producer feasibility and QA gating checks.

The producer feasibility check (PR-SPRINT) verifies scope viability, while the QA plan gate ensures testing readiness before finalizing. These gated workflows enforce scope and quality checks, requiring explicit user permission before writing the final sprint files.

Yes, you can update an existing sprint by pulling current context from production milestones, past sprint velocity, and available capacity. The process aggregates carryover, dependencies, and risks to emit an updated status report and sprint files.

Context-aware aggregation pulls data from production/milestones, production/sprints, design/gdd, and the risk register to assemble comprehensive sprint tasks. Having these artifacts available ensures accurate dependency mapping and readiness checks before sprint execution.

To avoid scope creep, use the provided definition-of-done checks and scope-check recommendations during sprint generation. Applying producer feasibility gates ensures the assembled tasks match available capacity before finalizing the sprint plan.

Sprint planning fails because unmapped dependencies bypass readiness checks, leading to blocked tasks and inaccurate capacity estimation. Aggregating dependencies from milestone and risk register data before producer review prevents these execution blockers.