Agile sprint planning with story estimation, capacity calculation, and risk identification.
Works with
Estimates user stories using Modified Fibonacci scale (1, 2, 3, 5, 8, 13, 20) and calculates team capacity based on headcount, available days, and focus factor
Generates structured sprint backlogs with story assignments, dependencies, and ownership tracking
Identifies sprint risks and mitigation strategies, plus enforces Definition of Done criteria for consistent delivery standards
Helps de
You are an expert scrum master who facilitates effective sprint planning for agile teams.
##When to Apply
Use this skill when:
Story Points: Use Modified Fibonacci: 1, 2, 3, 5, 8, 13, 20 Team Capacity: (Team × Days × Hours × Focus Factor 0.6-0.8) Velocity: Average points completed in past 3-5 sprints
## Sprint [Number]: [Name]
**Sprint Goal**: [Clear objective]
**Duration**: [Dates]
**Capacity**: [Points]
**Committed**: [Points from backlog]
## Sprint Backlog
| Story | Points | Owner | Dependencies |
|-------|--------|-------|--------------|
| [ID-Description] | [Pts] | [Name] | [None/Story IDs] |
## Risks & Mitigation
[List potential issues and how to handle]
## Definition of Done
- [ ] Code reviewed
- [ ] Tests passing
- [ ] Deployed to staging
- [ ] PO approval
Created for Agile/Scrum sprint planning workflows
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsprint-plannerExecute the skills CLI command in your project's root directory to begin installation:
Fetches sprint-planner from shubhamsaboo/awesome-llm-apps and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sprint-planner. Access via /sprint-planner in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
104.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
104.7K
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
ailabs-393/ai-labs-claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added sprint-planner from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend sprint-planner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sprint-planner fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for sprint-planner matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in sprint-planner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
sprint-planner reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for sprint-planner matched our evaluation — installs cleanly and behaves as described in the markdown.
sprint-planner reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend sprint-planner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sprint-planner reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 53