Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From jira
Assist with sprint planning, backlog grooming, and story point estimation. Use when planning sprints, estimating work, organizing backlog, or when user mentions sprint planning or story points.
npx claudepluginhub ramirez-justin/claude-plugins --plugin jiraHow this skill is triggered — by the user, by Claude, or both
Slash command
/jira:sprint-planningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Expert assistance for planning sprints, estimating work, and managing team capacity.
Structures sprint planning sessions: produces sprint goal, velocity-calibrated backlog, capacity plan, risk flags, and meeting agenda.
Recommends sprint scope by pulling backlog from Jira/Linear MCP or manual input, calculating team capacity from velocity and availability, and suggesting committed work, stretch goals, and deferred items.
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning or balancing scope against velocity.
Share bugs, ideas, or general feedback.
Expert assistance for planning sprints, estimating work, and managing team capacity.
For advanced velocity/capacity analysis: See the Advanced Capacity Analysis skill.
Review previous sprint:
sprint = "Sprint 42" ORDER BY updated DESC
Analyze: What completed? What carried over? What was velocity?
Check backlog health:
project = PROJ AND sprint IS EMPTY AND status = "To Do" ORDER BY priority DESC
Verify stories have descriptions, acceptance criteria, and estimates.
Define a clear, valuable objective:
Quick formula:
Capacity = Historical Velocity - (PTO adjustments) - (10% buffer)
Example: Velocity 40 pts, 1 person out 2 days → ~35 pts capacity
Criteria:
Query for candidates:
project = PROJ AND status = "To Do" AND sprint IS EMPTY
AND "Story Points" IS NOT EMPTY
ORDER BY priority DESC, rank ASC
Measure relative effort/complexity, not time:
| Points | Meaning | Example |
|---|---|---|
| 1 | Trivial | Config change, typo fix |
| 2 | Easy | Small, well-understood change |
| 3 | Moderate | Standard feature, clear path |
| 5 | Average | Typical feature, some complexity |
| 8 | Complex | Multiple components, higher uncertainty |
| 13 | Very Complex | Large feature, should consider splitting |
| 21 | Epic | Too large - must split |
Planning Poker:
Reference Stories: Compare to completed work
Increase for: New technology, unclear requirements, many integrations, high risk
Lower for: Familiar code, clear requirements, self-contained changes
Stories ready for sprint:
project = PROJ AND type = Story AND status = "To Do"
AND sprint IS EMPTY AND "Story Points" IS NOT EMPTY
ORDER BY priority DESC
Current sprint progress:
sprint in openSprints() ORDER BY status ASC, priority DESC
Unestimated stories:
project = PROJ AND "Story Points" IS EMPTY AND status != Done
ORDER BY priority DESC
When you need sprint planning assistance, I will:
You: "Help me plan Sprint 45. Team of 5, velocity around 35 points"
Me: "I'll help plan Sprint 45.
Capacity: ~30-32 points (with 10% buffer)
Let me search for ready stories:
[Uses /jira-search]
Recommended Sprint Backlog (31 points):
Sprint Goal: Complete basic payment flow
Stretch Goals:
Should I adjust the selection?"