pmstudio-comms

Generate stakeholder communications in Markdown from project context.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill pmstudio-comms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmstudio-comms
Source: https://github.com/rkz91/coco/tree/main/skills/stakeholder-comms
Command: npx skills add https://github.com/rkz91/coco --skill pmstudio-comms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stakeholder communications are time-consuming and error-prone when pulled together manually from scattered project artifacts.

Core Features & Use Cases

  • Template selection for Go-Live, Status, Onboarding, Change, Incident, and SteerCo updates.
  • Context-aware drafting pulls real names, dates, decisions, and roadmaps from project artifacts to pre-fill messages.
  • Ready-to-send Markdown outputs that can be pasted into emails, chat, or documentation.

Quick Start

Ask me to generate a Go-Live announcement, a Status update, or an Onboarding brief and I will produce a ready-to-send Markdown draft using the current project context.

Frequently Asked Questions about pmstudio-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate stakeholder communications from project memory and meeting notes?

Generate stakeholder communications by reading project memory, PRDs, meeting notes, and stakeholder directories to auto-populate real names, dates, and context into ready-to-send Markdown drafts.

What stakeholder communication templates are available for project updates?

Available templates cover Go-Live announcements, Status updates, Onboarding briefs, Change notifications, Incident summaries, and SteerCo updates, all produced as ready-to-send Markdown.

Can I automatically draft a Go-Live announcement using my existing project artifacts?

Yes, you can draft a Go-Live announcement by pulling real decisions, roadmaps, and context from project artifacts to pre-fill a ready-to-send Markdown message.

What is the best way to write a SteerCo update from scattered project documentation?

The best way is using context-aware drafting that reads scattered project documentation and stakeholder directories to populate a structured SteerCo update template with accurate details.

Does this approach output formatted Markdown for email and chat communications?

Yes, this approach outputs ready-to-send Markdown formatted for direct pasting into emails, chat platforms, or project documentation without requiring manual formatting.

Can I create an incident summary without manually searching through project decisions?

Yes, context-aware drafting automatically extracts relevant project decisions and context from your stored artifacts to populate the incident summary template, eliminating manual searches.