pmstudio-commslisted

Generate templated stakeholder communications from project context. Use when someone asks to "write a go-live email", "create a status update", "onboard someone", "write an announcement", "steerco update", "incident summary", "change notification", or any stakeholder communication task. Reads project memory, stakeholder directory, PRD, and meeting notes to pre-fill real names, dates, and context. Produces ready-to-send Markdown.
rkz91/coco · ★ 4 · AI & Automation · score 70

Install: claude install-skill rkz91/coco

# Stakeholder Comms — Templated Communications Generator ## Purpose Generates stakeholder communications pre-filled with project context. Not generic templates — these pull real stakeholder names, real dates, real scope from project artifacts. ## Process ### Step 1: Identify Template From user request or by asking: | Command | Template | When to Use | |---------|----------|-------------| | `/stakeholder-comms go-live` | Go-Live Announcement | Product/feature launching | | `/stakeholder-comms status` | Status Update | Periodic reporting (weekly/biweekly) | | `/stakeholder-comms onboard {name}` | Onboarding Brief | New team member joining | | `/stakeholder-comms change` | Change Notification | Planned change to live product | | `/stakeholder-comms incident` | Incident Summary | Post-incident communication | | `/stakeholder-comms steerco` | SteerCo Update | Leadership/governance meeting prep | If no subcommand, ask: "What type of communication do you need?" ### Step 2: Read Context **All templates read:** - `CLAUDE.local.md` — project overview, key decisions, stakeholders, recent changes - `.sync-watch.json` — project name **Template-specific reads:** | Template | Additional Sources | |----------|-------------------| | Go-Live | PRD (scope, success metrics), Meeting-Notes (launch decisions) | | Status | PRD (milestones, timeline), Meeting-Notes (recent), Change-Log (recent entries) | | Onboard | Stakeholder Directory, PRD (overview), Presentations (links to share) | |