# Pc Sprint Planning

> Use when the team has sized work and must choose a realistic iteration scope, sequence, and ownership model that fits capacity and current risk.

- Skill: `yknothing/pc-sprint-planning-2` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add yknothing/pc-sprint-planning-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yknothing/pc-sprint-planning-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: yknothing (https://skillmd.com/u/yknothing)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yknothing/pc-sprint-planning-2

---


# 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.

See [context](references/context.md) and [anti-pattern](references/anti-patterns.md) notes.

## Inputs

[I/O contract notes](references/io-contract.md) define required inputs and authority.

## Process

### Step 1: Start From Capacity, Not Desire

Confirm the real capacity for the iteration: available people, external blockers, carry-over work, and operational load. Adjust for on-call or release overhead when relevant.

### Step 2: Select Work That Fits the Goal

Choose the smallest set of tasks that:

- fits the available capacity
- preserves dependency order
- advances the sprint goal
- does not overload the team with too many simultaneous high-risk items

### Step 3: Make Sequence and Ownership Explicit

Document:

- what starts first
- what can run in parallel
- where handoffs occur
- which tasks are stretch goals versus committed work

### Step 4: Publish a Defensible Sprint Plan

The output should let anyone understand what the team is betting on, what was deferred, and which risks or assumptions could force replanning mid-sprint.

## Outputs

Produce only declared outputs at their documented quality boundary.

## Quality Gate

- [ ] Committed scope fits actual capacity
- [ ] Sequencing respects dependencies and major risks
- [ ] Stretch work is distinguished from committed work
- [ ] Deferred items are explicit
- [ ] The team can explain why the sprint is achievable