Turn a ready backlog and real team availability into a sprint commitment that fits. Reconcile carryover, calculate capacity, expose dependencies, compare scope options, and keep every owner decision traceable.
Sprint plans fail quietly when teams treat calendar days as capacity, roll unfinished work forward for free, or fill the board with items that still need decisions. This skill starts with the exact sprint dates, current backlog, team availability, fixed load, working agreements, carryover, and priority authority. Missing estimates, owners, acceptance criteria, and dependencies stay visible instead of becoming plausible guesses.
It builds separate ledgers for availability, committed load, conditional scope, stretch work, and reserve. Every candidate item passes a readiness check covering outcome, estimate, acceptance evidence, dependencies, required roles, review gates, and the smallest finishable slice. The workflow then produces a coherent sprint objective and compares feasible scope options before anyone calls the plan committed.
The handoff includes the sprint contract, input register, carryover reconciliation, capacity ledger, backlog readiness table, scope options, dependency and checkpoint register, risk controls, mutation preview, and owner decision record. It does not convert points to hours, use velocity as a performance target, edit a tracker without authorization, or claim the team accepted a plan without evidence.
Input
A six-person team has a two-week sprint, two people taking leave, one engineer on support, 18 points carried over, and 52 points of prioritized backlog. Two high-priority items lack acceptance criteria and one depends on an API another team has not committed to deliver.
Output
A reconciled capacity ledger, carryover decisions, readiness status for every item, a dependency checkpoint and fallback, two scope options, one outcome-level sprint objective, committed versus conditional and stretch work, reserve remaining, owner gates, and a planning-ready or commitment-ready verdict.
Input
The proposed sprint loads 46 points against a recent 31-35 point range. The product lead labels every item P0, three stories need the same mobile reviewer, and the board includes an unestimated migration plus a fixed release date. No interrupt reserve is shown.
Provide the sprint dates, product outcome, backlog snapshot, team roster and availability, estimation unit, recent completion evidence, carryover, definitions of ready and done, fixed obligations, dependencies, and planning authority. Ask the agent to prepare a new sprint, compare scope options, repair an overloaded plan, or reconcile a mid-sprint change. If estimates, availability, ownership, or critical dependencies are missing, the output stays at planning-ready or blocked instead of presenting a false commitment.
Sprint dates and time zone, planning owner, decision deadline, product outcome, release context, priority authority, estimation unit, and the team's definitions of ready and done.
A current backlog snapshot with source IDs, priorities, estimates, acceptance criteria, states, dependencies, owners, required roles, release gates, plus unfinished work from the prior sprint.
Team roster, leave, holidays, meetings, on-call or support load, non-sprint work, historical same-team completion evidence, reserve rule, skill bottlenecks, and tracker mutation authority.
SKILL.md; capacity, readiness, dependency, carryover, confidence, change-control, and verdict controls; reusable sprint contract, input, capacity, backlog, scope-option, dependency, risk, mutation-preview, decision, and mid-sprint change templates; OpenAI interface metadata
No reviews yet.
Output
A source-linked overload diagnosis, constrained-role capacity view, migration slice or exclusion, coherent goal options, explicit cut order, reserve policy decision, release and review dependencies, and a smaller plan that does not use velocity as a quota.
Input
On day four, a production defect needs an estimated eight points. The CTO says to add it immediately, but nobody recorded what leaves. Two committed items share the affected backend engineer, and the original sprint goal has already been announced.
Output
A preserved original plan, urgency and authority record, capacity and dependency impact, swap options, the exact item that moves or becomes at risk, a mutation preview, stakeholder handoff, and a changed state only after the new plan version is approved and verified.
Creator
Yyervan6
