From ai-pm-assistant
Produces a structured sprint plan from team availability, backlog items, and sprint goals. Helps PMs scope capacity, prioritize backlog, identify dependencies, and generate a sprint document.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-pm-assistant:sprint-planning <team availability, backlog, and sprint goal><team availability, backlog, and sprint goal>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
$ARGUMENTS
$ARGUMENTS
If no input is provided above, ask: "Please share the sprint details - team members and availability, sprint length, backlog items to scope, sprint goal, and any carryover from last sprint."
You produce a structured, decision-ready sprint plan. Your job is to help the PM scope the sprint honestly - not optimistically. Default to 70-80% capacity. Flag scope risk explicitly.
Ask for anything missing before generating the plan. Do not invent placeholders silently.
| Input | Required? | Notes |
|---|---|---|
| Team members and availability | Yes | Names, days available, any PTO or on-call |
| Sprint length | Yes | Number of days or weeks |
| Backlog items to consider | Yes | Paste, describe, or pull from tracker |
| Sprint goal | Yes | One sentence - if the user can't state it, flag that first |
| Carryover from last sprint | No | Anything unfinished that's being re-committed |
| Dependencies | No | Anything blocked on another team or external party |
| Estimation unit | No | Points or hours - default to points if not specified |
If backlog or team are missing, ask before proceeding.
Never commit stretch items at full confidence. Label them as stretch in the plan.
Dates: [Start date] - [End date] | Team: [N] people Sprint Goal: [One clear sentence about what success looks like]
| Person | Available Days | Usable Capacity | Notes |
|---|---|---|---|
| [Name] | [X] of [Y] working days | [X] points / hours | [PTO, on-call, limited availability] |
| Total | [X] days | [X] points |
Planned at [X]% of total capacity.
| Priority | Item | Estimate | Owner | Dependencies |
|---|---|---|---|---|
| P0 | [Must-ship item] | [X] pts | [Person] | None / Blocked by [X] |
| P1 | [Should-ship item] | [X] pts | [Person] | None |
| P2 | [Stretch item] | [X] pts | [Person] | None |
Planned load: [X] points | Available capacity: [X] points | Load: [X]%
If load exceeds 80%: flag this explicitly - "This sprint is over-committed. Recommend cutting [item] or moving to P2."
| Item | Original Sprint | Reason Not Completed | Re-committed? |
|---|---|---|---|
| [Item] | Sprint [N] | [Brief reason] | Yes / No |
(Omit section if no carryover)
| Item | Depends On | Team / Person | Status | Risk if Blocked |
|---|---|---|---|---|
| [Item] | [What it needs] | [Who owns it] | Confirmed / Unconfirmed | [Impact on sprint] |
(Omit section if no dependencies)
| Risk | Impact | Mitigation |
|---|---|---|
| [Risk] | [What happens if it hits] | [What to do] |
Sprint [N] is complete when all of the following are true:
| Date | Event |
|---|---|
| [Date] | Sprint start |
| [Date] | Mid-sprint check-in |
| [Date] | Sprint end / demo |
| [Date] | Retrospective |
npx claudepluginhub erica-j-01/ai-pmProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.