sprint-planning
Sprint Planning
Choose the next iteration on purpose. A sprint plan is a capacity-constrained bet, not a wish list.
Context
Sprint planning turns a backlog of valid work into a realistic short-horizon commitment. It is where business priority, engineering capacity, and delivery risk are forced into one explicit decision.
In Prodcraft, sprint planning should consume actual task, estimate, and risk artifacts. If it runs on optimism or memory, the system has already lost planning discipline.
Inputs
- task-list -- Candidate work for the iteration.
- estimate-set -- Size and confidence data for each task.
- risk-register -- The risks that should constrain commitment or sequencing.
Process
Step 1: Start From Capacity, Not Desire
More from yknothing/prodcraft
system-design
Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
6ci-cd
Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
6intake
The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
6feature-development
Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable implementation increment without expanding scope, breaking contracts, or hiding release-boundary risk.
6monitoring-observability
Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose real user-impactful boundaries, especially when brownfield coexistence rules, unsupported-flow safety, rollback health, or queue/backfill behavior must be visible before incidents escalate.
6incident-response
Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.
6