From role-pgm
Produce a weekly (or custom-window) team retrospective across projects. Aggregates shipped work, per-person contributions, themes, trends vs. last retro, wins, and specific growth areas anchored in real work. Complements status-report — status is for stakeholders, retro is for the team.
npx claudepluginhub sitloboi2012/team-marketplace --plugin role-pgmThis skill uses the workspace's default tool permissions.
**Invocation: user only.** Produces a retrospective draft; never auto-publishes or auto-posts.
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. Produces a retrospective draft; never auto-publishes or auto-posts.
Weekly or biweekly. The output is for the team to read together or async. It's a mirror — not a report for stakeholders. Use /role-pgm:status-report for upward reporting.
Parse $ARGUMENTS:
14d, 30d: longer windowscompare: compare the current window to the prior same-length window#ship and main project channels. Messages in the window with high reaction counts or deep reply threads — those are usually signal.If GitHub MCP isn't enabled, skip it — don't fabricate PR data.
Build a per-contributor picture. For each teammate:
Skip the per-person section if the team is solo or if there aren't enough distinct contributors to merit it.
Pull 2-4 themes across the window. These are the patterns, not the items. Good themes:
Bad themes (too generic):
If compare or if a prior retro exists in Notion, show deltas:
Last Now Delta
Shipped items 7 5 ↓2
Open blockers 2 4 ↑2
Risks at High 1 1 →
PRs opened 14 18 ↑29%
Cross-team meetings 6 9 ↑3
Pick 4-6 metrics that actually move the needle for this team. Don't invent metrics you can't measure. If it's the first retro, skip this section and note "first recorded — compare next week."
# Retro — <date range>
**TL;DR** <one sentence. The honest signal of the week. Good, bad, or flat.>
## By the numbers (optional, only if meaningful)
<4-6 line summary — shipped, blocked, risks, PRs, hotspots — only what's genuinely worth tracking for this team>
## Themes
- <theme> — <1-2 lines with specific evidence>
- <theme>
- <theme>
## Per person
**<Name>** — focused on <areas>
- Shipped: <1-3 specific outcomes>
- Praise: <specific thing, anchored in an artifact>
- Growth: <specific pattern if present>
<repeat per teammate>
## Top wins
- <3 specific wins, each with a link>
## Things to improve next window
- <3 specific, actionable items. Not "improve communication." "Stand up a 15-min mid-week sync for Project X until we unblock the design review queue." Anchor each in what happened this window.>
## Habits to try
- <2-3 small, realistic habits — each <5 min per day to adopt — that the team can trial next window>
## Open decisions / asks
- <anything the team needs a call on>
Show the draft. Common edits:
On approval, ask where it goes. Default options:
Never publish or post until the user explicitly approves the destination.