Sprint Planning Skill

Use When

Use when preparing a sprint goal, evidence-based team capacity, selected backlog, task breakdown, and delivery risks. Use definition-of-ready to admit individual items and definition-of-done to judge completed increments.

Do not use when a more specific upstream or downstream skill owns the task, or when the required project context has not been prepared.
Do not use this skill to fabricate missing project facts, legal conclusions, test results, approvals, or certification claims.

Artefact	Source or provider	Required?	Missing-input behaviour
Prioritised product backlog; sprint goal candidate; team availability and recent velocity; Definition of Ready results; dependency and leave calendar	Product owner, delivery team, and approved delivery metrics	Yes	Stop dependent work; name the missing item, owner, and decision impact. A review check remains `not assessed`.
Scope, audience, baseline/version, and accountable decision owner	Requester or project context	Yes	Ask for or record the gap; do not infer authority or scope.