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-industrial.md

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

Sprint Planning Example: Industrial

Team: Northfield firmware team (5 engineers), 2-week sprint, NFA-500 bring-up Dependency: a supplier radio-module sample promised for day 4 Why this example exists: a physical dependency with real lead time. The goal had to survive a late part.


## Sprint goal
> Firmware boots on the production NFA-500 board and reports a fault code over the service port.

Flexible: can be met on the dev board if the radio sample slips; the radio is the stretch.

## Capacity
| Person | Days | Leave/meetings | Focused |
|---|---|---|---|
| 5 engineers | 50 | 4 leave, 8 meetings, 5 lab-sharing | 33 |
**Focus factor:** 0.8 → ~26 days. Last three sprints finished 7, 8, and 6 items; plan 7.
**Slack held:** 2 items (about 25%): lab bookings fall through; board revisions arrive late.

## Selected work
| Order | Item | Ready? | Size |
|---|---|---|---|
| 1 | Bring up bootloader on production board | Yes | M |
| 2 | Fault-code table over service port | Yes | M |
| 3 | Watchdog configuration | Yes | S |
| 4 | Radio driver smoke test | **Blocked on sample** | M |
| Stretch | Power-cycle test rig script | Yes | S |

## Risks and dependencies
| Item | Owner | Needed by | Fallback |
|---|---|---|---|
| Radio sample | Supply chain lead | Day 4 | Move item 4 to next sprint; goal unaffected |
| Lab slot for thermal test | Test lead | Day 6 | Book a backup slot on day 8 |
**Most likely to break the goal:** the production board revision arriving late.

## Commitment
Believed with one condition: if the board slips past day 2, drop to the dev board and re-plan.

What to learn from this

  • The goal doesn't depend on the late part, so the supplier slipping costs scope, not success.
  • Slack is larger (25%) because physical lead times are less forgiving.
  • The condition is named in advance, so the day-two decision is already made.

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