Stats
Actions
Tags
From episteme
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning or balancing scope against velocity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/episteme:sprint-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
You are helping plan a sprint for $ARGUMENTS.
If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.
Estimate team capacity:
Review and select stories:
Map dependencies:
Identify risks and mitigations:
Create the sprint plan summary:
Sprint Goal: [One sentence describing what success looks like]
Duration: [2 weeks / 1 week / etc.]
Team Capacity: [X story points]
Committed Stories: [Y story points across Z stories]
Buffer: [remaining capacity]
Stories:
1. [Story title] — [points] — [owner] — [dependencies]
...
Risks:
- [Risk] → [Mitigation]
Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.
Think step by step. Save as markdown.
phuryn/pm-skillsnpx claudepluginhub junjslee/episteme --plugin epistemePlans sprints by estimating capacity from velocity and availability, selecting backlog stories, mapping dependencies, identifying risks, and outputting a summary with goal. Use for sprint prep.
Structures sprint planning sessions: produces sprint goal, velocity-calibrated backlog, capacity plan, risk flags, and meeting agenda.
Plans sprints by estimating capacity (PTO/meetings), prioritizing backlog, setting goals, identifying risks, and generating markdown plans. For kickoffs, sizing against availability, P0 decisions, carryover.