sprint-planning | SkillBundle

/sprint-planning

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Plan a sprint by scoping work, estimating capacity, and setting clear goals.

Usage

/sprint-planning $ARGUMENTS

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                    SPRINT PLANNING                                 │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ Define sprint goals and success criteria                     │
│  ✓ Estimate team capacity (accounting for PTO, meetings)        │
│  ✓ Scope and prioritize backlog items                           │
│  ✓ Identify dependencies and risks                              │
│  ✓ Generate sprint plan document                                │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + Project tracker: Pull backlog, create sprint, assign items   │

What I Need From You

Team: Who's on the team and their availability this sprint?
Sprint length: How many days/weeks?
Backlog: What's prioritized? (Pull from tracker, paste, or describe)
Carryover: Anything unfinished from last sprint?
Dependencies: Anything blocked on other teams?

Output

Tips

Leave buffer — Plan to 70-80% capacity. You will get interrupts.
One clear sprint goal — If you can't state it in one sentence, the sprint is unfocused.
Identify stretch items — Know what to cut if things take longer than expected.
Carry over honestly — If something didn't ship, understand why before re-committing.

/sprint-planning

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Plan a sprint by scoping work, estimating capacity, and setting clear goals.

Usage

/sprint-planning $ARGUMENTS

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                    SPRINT PLANNING                                 │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ Define sprint goals and success criteria                     │
│  ✓ Estimate team capacity (accounting for PTO, meetings)        │
│  ✓ Scope and prioritize backlog items                           │
│  ✓ Identify dependencies and risks                              │
│  ✓ Generate sprint plan document                                │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + Project tracker: Pull backlog, create sprint, assign items   │

What I Need From You

Team: Who's on the team and their availability this sprint?
Sprint length: How many days/weeks?
Backlog: What's prioritized? (Pull from tracker, paste, or describe)
Carryover: Anything unfinished from last sprint?
Dependencies: Anything blocked on other teams?

Output

Tips

Leave buffer — Plan to 70-80% capacity. You will get interrupts.
One clear sprint goal — If you can't state it in one sentence, the sprint is unfocused.
Identify stretch items — Know what to cut if things take longer than expected.
Carry over honestly — If something didn't ship, understand why before re-committing.