sprint-plan

Sprint plan generation organizes milestone context, prior sprint history, and risk information into actionable work items. It produces a structured plan with capacity breakdowns, must/should/nice task tables, carryover items, risks, and a clear definition of done.

Sprint status reporting generates an up-to-date progress report by categorizing work into completed, in-progress, not-started, and blocked items. It also provides a burndown assessment and highlights emerging risks to keep delivery status transparent.

QA gating enforces the presence or explicit handling of a sprint QA plan before allowing sprint planning to proceed. This workflow guardrail ensures production-focused development workflows meet acceptance criteria and maintain quality standards.

Yes, you can run sprint-plan in update mode to refresh sprint tasks based on the current milestone and what has already been completed. This mode also reviews producer feasibility and QA readiness to adjust the plan accurately.

Sprint planning requires production milestone context, sprint history, risk register inputs, and design backlog readiness signals. The process parses these inputs alongside team capacity to generate a realistic and actionable sprint plan.

Yes, sprint-plan optionally writes a sprint-status.yaml machine-readable truth source. This file captures the generated sprint plan and progress data, enabling downstream production workflows and automated tracking systems to consume the status directly.