sprint-plan

Name: sprint-plan
Author: phuryn

1.7kinstalls2.5kforks

How to install sprint-plan?

phuryn/pm-skills/sprint-plan

$npx -y skills add phuryn/pm-skills --skill sprint-plan

Installs into the current project.

Summary

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Files · 1

View on GitHub

SKILL.md

1	## Sprint Planning
2
3	Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
4
5	### Context
6
7	You are helping plan a sprint for $ARGUMENTS.
8
9	If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.
10
11	### Instructions
12
13	1. Estimate team capacity:
14	- Number of team members and their availability (PTO, meetings, on-call)
15	- Historical velocity (average story points per sprint from last 3 sprints)
16	- Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
17	- Calculate available capacity in story points or ideal hours
18
19	2. Review and select stories:
20	- Pull from the prioritized backlog (highest priority first)
21	- Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
22	- Flag stories that need refinement before committing
23	- Stop adding stories when capacity is reached
24
25	3. Map dependencies:
26	- Identify stories that depend on other stories or external teams
27	- Sequence dependent stories appropriately
28	- Flag external dependencies and owners
29	- Identify the critical path
30
31	4. Identify risks and mitigations:
32	- Stories with high uncertainty or complexity
33	- External dependencies that could slip
34	- Knowledge concentration (only one person can do it)
35	- Suggest mitigations for each risk
36
37	5. Create the sprint plan summary:
38
39	```
40	Sprint Goal: [One sentence describing what success looks like]
41	Duration: [2 weeks / 1 week / etc.]
42	Team Capacity: [X story points]
43	Committed Stories: [Y story points across Z stories]
44	Buffer: [remaining capacity]
45
46	Stories:
47	1. [Story title] — [points] — [owner] — [dependencies]
48	...
49
50	Risks:
51	- [Risk] → [Mitigation]
52	```
53
54	6. Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.
55
56	Think step by step. Save as markdown.
57
58	---
59
60	### Further Reading
61
62	- [Product Owner vs Product Manager: What's the difference?](https://www.productcompass.pm/p/product-manager-vs-product-owner)

People who liked this also viewed

6 picks

Type

sprint-plan

1.7kinstalls2.5kforks

View on GitHub

How to install sprint-plan?

phuryn/pm-skills/sprint-plan

$npx -y skills add phuryn/pm-skills --skill sprint-plan

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Sprint Planning
2
3	Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
4
5	### Context
6
7	You are helping plan a sprint for $ARGUMENTS.
8
9	If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.
10
11	### Instructions
12
13	1. Estimate team capacity:
14	- Number of team members and their availability (PTO, meetings, on-call)
15	- Historical velocity (average story points per sprint from last 3 sprints)
16	- Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
17	- Calculate available capacity in story points or ideal hours
18
19	2. Review and select stories:
20	- Pull from the prioritized backlog (highest priority first)
21	- Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
22	- Flag stories that need refinement before committing
23	- Stop adding stories when capacity is reached
24
25	3. Map dependencies:
26	- Identify stories that depend on other stories or external teams
27	- Sequence dependent stories appropriately
28	- Flag external dependencies and owners
29	- Identify the critical path
30
31	4. Identify risks and mitigations:
32	- Stories with high uncertainty or complexity
33	- External dependencies that could slip
34	- Knowledge concentration (only one person can do it)
35	- Suggest mitigations for each risk
36
37	5. Create the sprint plan summary:
38
39	```
40	Sprint Goal: [One sentence describing what success looks like]
41	Duration: [2 weeks / 1 week / etc.]
42	Team Capacity: [X story points]
43	Committed Stories: [Y story points across Z stories]
44	Buffer: [remaining capacity]
45
46	Stories:
47	1. [Story title] — [points] — [owner] — [dependencies]
48	...
49
50	Risks:
51	- [Risk] → [Mitigation]
52	```
53
54	6. Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.
55
56	Think step by step. Save as markdown.
57
58	---
59
60	### Further Reading
61
62	- [Product Owner vs Product Manager: What's the difference?](https://www.productcompass.pm/p/product-manager-vs-product-owner)

People who liked this also viewed

6 picks

Type