comms

Synthesize stakeholder-aligned communications updates from cross-functional signals for leadership decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/namankumar/product-os --skill comms-namankumar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comms
Source: https://github.com/namankumar/product-os/tree/main/.claude/skills/comms
Command: npx skills add https://github.com/namankumar/product-os --skill comms-namankumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product leaders craft consistent, narrative-aligned leadership and investor updates by synthesizing context from current narratives, OKRs, and stakeholder dynamics, so decisions are informed and aligned.

Core Features & Use Cases

  • Leadership updates for founders and executives that articulate impact and next steps.
  • Team announcements that surface coordination across engineering, design, and GTM.
  • Cross-functional status updates that connect delivery progress to strategy and OKRs.
  • Investor/board briefs that present momentum, risks, and decisions with crisp narratives.
  • Narrative alignment with active strategy and roadmaps to maintain coherence across communications.

Quick Start

Draft a leadership update for {{PRODUCT}} showing the latest win and the next actions, using the latest context from context/current-context.md and contextual narratives from docs and room profiles.

Frequently Asked Questions about comms

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

FAQPage Schema
How do I craft leadership updates that align with current OKRs and stakeholder narratives?▼

To craft leadership updates that align with OKRs and stakeholder narratives, synthesize cross-functional signals from current context files and master strategy docs to inform executive decisions.

What is the best way to synthesize cross-functional status reports for investor briefs?▼

Synthesizing cross-functional status reports for investor briefs involves connecting delivery progress to strategy and OKRs, presenting momentum and risks with crisp narratives.

How do I write team announcements that surface coordination across engineering, design, and GTM?▼

Writing team announcements that surface coordination across engineering, design, and GTM requires synthesizing cross-functional signals to articulate impact and next steps for stakeholders.

Do I need to load context files before generating stakeholder-aligned comms updates?▼

Yes, loading context from context/current-context.md, context/narrative-map.md, and master strategy docs is required to ensure stakeholder-aligned comms updates match current narratives and goals.

Can I use this approach for both executive leadership updates and board briefs?▼

Yes, this approach applies to leadership updates, team announcements, investor briefs, and cross-functional status reports, ensuring coherent narrative alignment across all executive communications.

When should I not use automated narrative synthesis for leadership comms?▼

Avoid using automated narrative synthesis for leadership comms when current context files, narrative maps, or master strategy docs are unavailable, as alignment with active strategy requires these inputs.