From role-pgm
Plan one iteration of work — a sprint (Scrum), a cycle (Shape Up), or a weekly commit (Kanban). Sets the iteration goal, selects work based on capacity and velocity, defines the commitment, and flags risks. Use at iteration kickoff.
npx claudepluginhub sitloboi2012/team-marketplace --plugin role-pgmThis skill uses the workspace's default tool permissions.
**Invocation: user only.**
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Invocation: user only.
Plans one iteration, whatever the team's framework is. Supports three:
Parse $ARGUMENTS. If framework isn't explicit, ask the user — different frameworks have different plan outputs.
One sentence. What the team commits to producing or making progress on. Not a list of tasks — a goal.
Good: "Ship the export-to-CSV feature to 10% of customers and validate adoption > 20%." Bad: "Close 8 tickets."
Scrum:
Shape Up:
Kanban:
Scrum: build the sprint backlog For each story selected, record: ID, estimate (modified Fibonacci: 1, 2, 3, 5, 8, 13, 20), owner, hard dependencies. Sum estimates ≤ commit target. Stories >13 points should be split or flagged — they hide risk.
Shape Up: shape the pitch For the pitch(es) this cycle, confirm: problem is bounded, appetite is honest, no-gos are explicit, fat-marker sketches of solution exist. Reject anything vague or unboxed. A pitch without clear no-gos will consume the cycle.
Kanban: define the pull priority Ordered list of items. WIP limit per column. Work begins at the top; lower items are context, not commitments.
For the selected work, identify:
If any of these are material, either cut work or acknowledge the risk in the commitment.
For each item selected, the team must agree on the done bar:
Default done-bars per iteration so the team doesn't re-negotiate each item.
# Sprint plan: <sprint N>
**Goal:** <one-sentence commitment>
**Duration:** <start — end> (<N days>)
**Velocity (trailing 3 sprints):** <points avg>
**Capacity this sprint:** <hours> (team × days × 0.7 focus factor, minus PTO)
**Commit target:** <points>, ~80% of capacity
## Sprint backlog
| # | Story | Estimate | Owner | Depends on |
| --- | --- | --- | --- | --- |
| 1 | <story> | 5 | <person> | — |
| 2 | ... | | | |
**Total committed:** <points>
**Stretch (if capacity opens):** <1-2 stories>
## Carryover from last sprint
- <item> — status — action (commit / drop / push)
## Risks
- <risk> — mitigation
## Definition of done (this sprint)
- [ ] Code merged to main
- [ ] Tests passing
- [ ] Reviewed by 1 engineer + designer on UI items
- [ ] Deployed to staging
- [ ] Feature-flagged or launched
- [ ] Stakeholder demo at end of sprint
# Cycle plan: <cycle start date>
**Duration:** 6 weeks (or 2-week small-batch) — <start — end>
**Teams:** <list — usually pairs>
## Pitch 1: <name>
**Appetite:** <2w | 6w>
**Problem:** <bounded>
**Solution outline:** <fat-marker sketch, high level>
**No-gos:** <explicit scope exclusions>
**Team:** <pair>
**Risks:** <flagged rabbit holes, dependencies>
## Pitch 2: ...
## Cooldown (after cycle)
<what we'll do in the 2 weeks between cycles — maintenance, exploration, team rest>
# Week commit: <week start>
**Goal:** <one sentence>
**WIP limits:** To Do ∞ / In Progress 3 / Review 2 / Done ∞
## Pull priority (top-down)
1. <item> — owner
2. <item> — owner
3. ...
## Hard dependencies and ordering
- <item> must precede <item> because <reason>
## Expected done by end of week
<which items we expect to hit "done" — realistic given WIP limits>
## Risks
- <risk>
Show the draft. Common edits:
On approval: publish to the team's tracker (Notion / Jira / Linear via the appropriate MCP if connected), post kickoff summary to Slack via /team-core:draft-email flow. The kickoff post should be short — the goal, the commitment, the top risks. Team members check the tracker for detail.
Methodology inspired by the shubhamsaboo "sprint-planner" skill, extended for Shape Up and Kanban frameworks.