Index of every page on this site: llms.txt
All skills
deanpeters avatar

/sprint-planning

@476ae12
Run it yourself

Plan a sprint around a goal, real capacity, and named risks. Use when a team's sprints end with carryover, a pile of unrelated tickets, or a goal nobody can state.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/sprint-planning

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample.md

≈524 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Sprint Planning Example: SaaS

Team: Fieldlight onboarding squad (6 engineers, 1 designer), 2-week sprint Last sprint: planned 14, completed 9, carried 5 (third sprint in a row near 65%) Why this example exists: the team's list was 14 tickets with no goal. A goal and honest capacity turned it into a plan the team believed.


## Sprint goal
> A new dispatcher can load a day and run their first optimization without asking for help.

Specific (observable in a usability session) · Valuable (the 7-day activation gap) · Flexible (guided
tour, defaults, or error messages could each get there).

## Capacity (set by the team)
| Person | Days | Leave/meetings/support | Focused |
|---|---|---|---|
| 6 engineers | 60 | 3 leave, 9 meetings, 6 support rotation | 42 |
| Designer | 10 | 2 meetings | 8 |
**Focus factor:** 0.75 → ~31 focused days of work.
**Recent throughput:** 9-10 items; plan for 10, not 14.
**Slack held:** 2 items (20%): production issues and review.

## Selected work (serves the goal)
| Order | Item | Ready? | Size |
|---|---|---|---|
| 1 | Default depot address from the account | Yes | S |
| 2 | First-run guided tour for load-day | Needs refinement (copy) | M |
| 3 | Error message when day has no jobs | Yes | S |
| 4 | Sample day data for trials | Yes | M |
| Stretch | Tooltip on "movable" jobs | Yes | S |
**Dropped from the list:** 6 tickets that don't serve the goal (moved to backlog, not lost).

## Risks and dependencies
| Item | Owner | Needed by | Fallback |
|---|---|---|---|
| Tour copy from Marketing | Sam | Day 3 | Ship with placeholder copy, replace in Sprint +1 |
**Most likely to break the goal:** the tour copy.

## Commitment
Team believes it: yes. Review point: day five, check item 2.

What to learn from this

  • Six tickets left the sprint because they didn't serve the goal. Nothing was deleted.
  • The plan is 10 items against 14 hoped for. Three sprints of data set the number, not the PM.
  • A fallback sits next to the one external dependency, so a late copy slips the polish, not the goal.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    The skill is a project management workflow for sprint planning. It provides templates and instructions for setting goals and assessing team capacity without using any executable code, network operations, or external dependencies.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: LOW · No issues

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the team, the sprint length, and the backlog you're planning from]
type
workflow
theme
pm-artifacts
Other metadata
intent
Run sprint planning as a decision about what the team can commit to and why, not a ticket-filling exercise. Starts from a sprint goal, sizes capacity from real availability, selects work that serves the goal, holds slack for the unplanned, names the risks and dependencies, and leaves a commitment the team believes. Works for software sprints and for hardware or service teams on a fixed cadence.
best_for
[
  "Planning a sprint around one goal instead of a list of tickets",
  "Fixing chronic carryover by sizing to real capacity",
  "Making risks and dependencies visible before the sprint starts",
  "Teams on a fixed cadence outside pure software (hardware, service, ops)"
]
scenarios
[
  "Every sprint we carry a third of the work over. Help me plan this one differently",
  "We have 6 people, two on leave, and 40 tickets. What goes in?",
  "Write a sprint goal for a sprint that is mostly bug fixes",
  "Plan a two-week cadence for a hardware firmware team with a supplier dependency"
]
estimated_time
30-60 min

README badge

README badge for deanpeters/product-manager-skills/sprint-planning