From role-pgm
Produce a weekly (or custom-window) project status report aggregating shipped work, in-flight items, blockers, and risks from Notion, Slack, and GitHub. Drafts only — publishing goes through confirmation.
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.
Parse $ARGUMENTS:
If "all" and there are >5 active projects, ask the user to pick or confirm.
For each project in scope, in parallel:
For each project, produce:
A "blocker" is a specific thing stopping specific work. "Capacity" is not a blocker unless the capacity is missing for an identified reason.
# Status — <date range>
**TL;DR** <one sentence. Biggest signal. "On track except X." or "Two new blockers this week.">
## Project: <name>
**Owner:** <person> · **Health:** 🟢 on track | 🟡 watch | 🔴 at risk
**Shipped this window**
- <item>
**In flight**
- <item> — <owner> — <% or "started/mid/wrapping"> — landing <date>
**Blockers**
- <blocker> — blocked <N days> — needs <owner to unblock>
**Risks**
- <risk> (<severity>) — <mitigation status>
**Decisions needed**
- <decision> — by <date>
---
[repeat per project]
## Cross-cutting notes
<anything that affects multiple projects>
Health rubric:
Be honest with the color. A green light that should be yellow is the worst kind of report.
Show the draft. Ask:
Publish only after approval. Use /team-core:draft-email flow for email.