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.

template.md

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

Sprint Planning Template

The team sets capacity and estimates. Unsupplied figures stay [NEEDS SOURCE].


1. Context

Team: · Sprint length / dates: · Last sprint: planned / completed / carried: Last three sprints' throughput: [NEEDS SOURCE if unknown]

2. Sprint goal (one sentence, an outcome)

[goal] Specific? ☐ Valuable? ☐ Flexible (more than one way)? ☐

3. Capacity (set by the team)

Person Days in sprint Leave / meetings / support Focused days Notes
Focus factor: · Team capacity: · Checked against recent throughput: ☐
Slack held (share, what it absorbs):

4. Selected work

Order Item Serves goal how Ready? (understood, small, done defined) Size (team's) Stretch?

Total vs capacity less slack:

5. Risks and dependencies

Dependency / risk Owner Needed by Fallback if it slips
Most likely to break the goal:

6. Commitment

The team believes this plan: yes / no / with conditions: ____ Review point: [day five check]


Quality checks

  • Goal is specific, valuable, and flexible, written before the tickets
  • Capacity is available focused hours, checked against recent throughput
  • The team, not the PM, set the number
  • Slack is held and its purpose named
  • Every item serves the goal and is ready
  • Every dependency has an owner, a date, and a fallback
  • The team said aloud whether they believe it

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