Sprint Planner
A Claude skill from aakashg/pm-claude-code-setup.
Install
$ agentstack add skill-aakashg-pm-claude-code-setup-sprint-planner ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-aakashg-pm-claude-code-setup-sprint-planner) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Sprint Planner
Trigger
Activate on "plan sprint", "sprint planning", "what should we work on", "organize the backlog".
Behavior
Step 1: Get Input
Ask:
- Paste the backlog (titles, priorities, estimates)
- Team size
- Sprint duration (1 or 2 weeks)
- Any constraints or deadlines
Step 2: Plan
Sprint Goal (1 sentence)
Recommended Backlog | Item | Estimate | Priority | Dependencies | Owner |
Capacity Check
- Capacity: [X points/days]
- Planned: [total]
- Buffer (20%): [amount]
- Verdict: Over/Under/Right-sized
Stretch Goals (if team finishes early)
Risks to This Sprint
Example
Bad sprint plan (no capacity math, no priorities):
Sprint Goal: Work on stuff
Items: Auth, Dashboard, Bugs, API, DocsGood sprint plan:
Sprint Goal: Ship auth migration to 100% of web users
Capacity: 3 engineers x 10 days = 30 eng-days. At 80% = 24 available.
| Item | Estimate | Priority | Dependencies | Owner |
|------|----------|----------|-------------|-------|
| Auth migration: 40% → 100% rollout | 8d | P0 | QA sign-off (due Mon) | Jake |
| Mobile session bug fix | 5d | P0 | Root cause analysis (done) | Sarah |
| Dashboard loading perf | 3d | P1 | None | Alex |
| API rate limit docs | 2d | P2 | None | Jake |
Planned: 18 eng-days | Buffer: 6 eng-days | Verdict: Right-sized
Stretch Goals:
- Begin Outlook calendar sync research (3d) — only if auth ships by Thursday
Risks:
- Mobile bug fix estimate is uncertain. If root cause is deeper than
diagnosed, it could take 8d instead of 5d. Mitigation: Jake pairs
with platform team. If not resolved by Wednesday, descope and carry
to next sprint.Rules
- 80% capacity is the ceiling. Sprints loaded above 80% have a >50% chance of missing the goal.
- Flag items with unclear requirements. Unclear requirements are estimation landmines.
- Unresolved dependencies block sprint entry. Resolve before committing the item.
- Every item needs a definition of done.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: aakashg
- Source: aakashg/pm-claude-code-setup
- License: MIT
- Homepage: https://www.news.aakashg.com/p/pm-os
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.