What you'll learn: How Claude Code handles the five recurring communication tasks that drain PM teams — weekly updates, release notes, customer announcements, board decks, and meeting agendas — and how shared context makes every output consistent.
Stakeholder communication is the most predictable time sink in product management. Every Friday, the update is due. Every release, the notes need writing. Every board meeting, the product narrative needs structuring. Every customer-facing launch, the announcement needs drafting.
None of this is difficult work. All of it is time-consuming. And because it's predictable — same format, same audience, same cadence — it's exactly the kind of work where AI makes the biggest difference.
This is the deep dive on the Communication category from 7 Types of PM Work You Can Automate with Claude Code. If you haven't read that overview, it covers all seven PM automation categories.
Why Communication Work Drains PM Teams
Product managers communicate in at least four directions: up (executives and board), down (engineering and design), out (customers and prospects), and across (sales, support, marketing). Each audience wants different things. Each format has different requirements. And the PM is the single point of translation between what happened in the product and what each audience needs to know.
For PM teams, this translation work hits disproportionately hard. There's no product marketing team to draft customer announcements. No chief of staff to compile the board update. No dedicated release manager to write the notes. The PM does all of it — alongside the actual product work that generates the things worth communicating.
The result is a predictable pattern: communication becomes the task that gets squeezed. The update goes out late. The release notes are thin. The board deck gets assembled the night before. Not because the PM doesn't care about communication, but because communication competes with everything else for a finite number of hours.
AI handles the structured parts of communication — assembling context, applying the right format, producing a first draft — so the PM focuses on the parts that require judgment: what to emphasize, what to flag, what to ask for.
As much as I appreciate the outputs AI creates for communication, you still need to put your final stamp on every artifact. AI will get you 90% of the way there — especially with good context files. But make sure the output is in your voice and something you're comfortable sharing across the org. The structure and data come from the system. The framing and judgment come from you.
The Weekly Update: From Scramble to System
The executive update is the most frequent and the most dreaded PM communication task. It happens every week. It should take 30 minutes. It usually takes 90.
The Update Problem
Friday at 4 PM. The PM opens last week's update template, hoping to modify it. Half the items are stale. They start reconstructing the week from memory: What shipped? What slipped? What blocked? What decisions are pending?
The information exists — scattered across Jira tickets, Slack threads, standup notes, and the PM's memory. Assembling it into a coherent narrative is the bottleneck. Not the writing. The gathering.
Then there's the framing problem. An executive update isn't a list of tasks completed. It's a narrative that connects product activity to business outcomes. The VP of Sales doesn't care that the team closed 14 tickets. They care that the integration blocking the Q2 deal is on track. The CEO doesn't want a feature list. They want to know whether the quarter's objectives are tracking.
Translating "what we did" into "what it means" takes judgment. But most of the PM's 90 minutes goes to the gathering step, not the judgment step. By the time they've assembled the facts, they're out of time for the framing.
How /executive-update-generator Works
The /executive-update-generator skill reads your product context — current priorities, roadmap milestones, and strategic objectives from your context files. It produces a structured update covering what shipped this period, what's in progress with expected completion, what's blocked and what's needed to unblock, and what decisions are pending from leadership.
The output isn't a raw activity log. It's framed around the things executives care about: progress against objectives, risks that need attention, and decisions that need making. The structure is consistent every week, which means the executive audience learns where to look for what matters to them.
The PM reviews the draft, adjusts emphasis, adds context that only they know (the conversation with the customer that changes the priority, the engineering concern that hasn't surfaced in tickets yet), and sends. Total time: 20 minutes instead of 90.
Example — Over a year, that difference adds up to roughly 60 hours — more than a full work week recovered from a single recurring task. And because the format is consistent every week, the executive audience learns where to look for what matters.
Team-Wide Communication Consistency
When every PM on a team uses the same update skill, the Head of Product gets consistent inputs. Same format. Same sections. Same level of detail. The Monday leadership meeting stops being a round of "let me re-explain what my team did" and becomes a conversation about trade-offs and priorities.
This consistency matters more than most teams realize. When updates look different from every PM, the executive audience spends mental energy parsing format instead of evaluating content. When updates look the same, the audience can compare across product areas, spot patterns, and make decisions faster.
Release Notes: One Event, Multiple Audiences
A feature ships. Now you need to tell people about it. But "people" isn't one audience. It's several: existing customers who'll use the feature, prospects evaluating your product, internal teams who need to understand it, and potentially press or analysts tracking your space.
The Release Notes Problem
Most release notes are written once, for one audience, and they serve none of them well. They're too technical for customers. Too shallow for engineering. Too feature-focused for sales. The PM writes them in a rush after the release, and the result reads like a changelog with aspirations.
The deeper problem is that release notes are a translation exercise. The raw material — what the engineering team built — needs to be translated into language that resonates with each audience. A database migration becomes "faster load times." A new API endpoint becomes "connect your tools in minutes." A refactored auth flow becomes "simpler, more secure login."
Doing this translation well for one audience takes 30 minutes. Doing it for three or four audiences takes half a day. Most PMs don't have half a day, so they write one version and hope it works for everyone. It doesn't.
How /release-notes-pro Works
The /release-notes-pro skill takes the technical reality of what shipped and produces release notes calibrated to different audiences. It reads your product context and persona files to understand who uses what, and frames each note in language that resonates with the target audience.
A single feature gets multiple treatments: the customer-facing version emphasizes benefit and use case, the internal version covers technical detail and known limitations, and the sales-facing version highlights competitive advantage and talk tracks.
The PM isn't writing three documents from scratch. They're reviewing and refining three drafts that already speak the right language to the right audience.
Customer Announcements
For major releases that warrant dedicated customer communication, /customer-announcement-writer produces the announcement — email, in-app notification, or blog post format. It references your product positioning and persona files to ensure the announcement connects the feature to the problems your customers actually have.
This is where context files earn their keep. A customer announcement written without persona context is generic: "We're excited to announce Feature X." An announcement written with persona context is specific: it addresses the workflow the feature improves, the pain it eliminates, and the outcome the customer can expect.
The difference between those two announcements is the difference between a feature that gets adopted and one that gets ignored.
Board Decks: Product Narrative Under Pressure
Board meetings are the highest-stakes communication event for most PM leaders. The audience is sophisticated, the time is limited, and the expectations are high. A good board-level product narrative builds confidence. A bad one raises questions that take weeks to answer.
The Board Deck Problem
Most product sections in board decks are assembled in a panic. The board meeting is in two days. The CEO needs the product slides. The Head of Product pulls up the last deck, realizes half of it is stale, and spends an evening rebuilding.
The challenge isn't slide design. It's narrative architecture. A board-level product update needs to connect the dots: here's our strategy, here's what we executed against it, here's what we learned, here's what we're doing next, and here's what we need from the board. Each piece builds on the previous one. Miss a connection and the narrative falls apart.
Building that narrative from scratch every quarter is where the time goes. Not in the writing — in the thinking about structure and flow while simultaneously trying to assemble the facts.
How /board-deck-generator Works
The /board-deck-generator skill produces a board-ready product narrative. It reads your strategic context — OKRs, product roadmap, competitive landscape — and structures a narrative that connects strategy to execution to results to next steps.
The output covers strategic priorities and progress against them, key product milestones and outcomes, competitive positioning and market dynamics, risks and what's being done about them, resource needs and investment asks, and the forward-looking roadmap with rationale.
The PM gets a structured narrative draft that they edit for nuance and emphasis. The facts are assembled. The connections between strategy and execution are drawn. The PM adds the judgment — what to highlight, what to downplay, what to ask for.
For Heads of Product who report to a board, this skill eliminates the quarterly panic. The narrative structure is consistent across quarters, which means the board can track progress over time instead of re-parsing a different format every meeting.
Meeting Agendas: Small Task, Outsized Impact
Meeting agendas are the smallest communication task on this list. They're also the one with the highest return per minute invested. A focused agenda with clear objectives, decision points, and pre-read materials turns a 60-minute meeting into 30 minutes of productive conversation. A missing or vague agenda turns 30 minutes into 60 minutes of wandering.
How /meeting-agenda Works
The /meeting-agenda skill creates focused meeting agendas with objectives, discussion topics with time allocations, decision points that need resolution, required pre-reads, and assigned owners for each topic.
For recurring meetings — sprint reviews, stakeholder syncs, planning sessions — the skill produces agendas grounded in your current product context. The sprint review agenda references what's actually in the sprint. The stakeholder sync covers the topics that matter this week, not a generic template from six months ago.
For PMs who run multiple recurring meetings per week, the cumulative time savings from better agendas — shorter meetings, fewer follow-ups, clearer decisions — compounds significantly.
The Communication System
Each of these skills works independently. Together, they form a communication system where every output references the same product context.
The weekly executive update and the quarterly board narrative tell the same story at different altitudes. The release notes and the customer announcement use the same positioning language. The meeting agenda and the stakeholder update reference the same priorities.
This consistency doesn't happen when each communication artifact is written from a blank page. It happens when every skill reads the same context files — the same product description, the same strategic priorities, the same persona definitions.
The practical effect: a Head of Product can review communication across the team and find a coherent narrative, not four PMs telling four different stories about the same product.
How Communication Connects to Strategy
Communication skills produce better output when they reference other strategic artifacts. An executive update that connects to your OKRs (from /okr-coach) tells a more compelling story. Release notes that reference your positioning (from /positioning-statement-generator) use more consistent language. A board deck that accounts for your competitive landscape (from /competitive-profile-builder) addresses the questions the board will actually ask.
Tip — This is the compounding effect of a system where every skill reads the same context. Your strategy work, specs, competitive intelligence, and communication all draw from the same foundation. Each artifact reinforces the others.
Watch out — AI-generated communication handles structure and consistency well, but it can't read the room. Political dynamics, unspoken concerns, and the framing that works for a specific executive's communication style — those require the PM's judgment. Review every outward-facing artifact with your audience's context in mind, not just the content's accuracy.
Getting Started with AI Communication
Communication is the easiest place to start with AI skills. The tasks are frequent, the format is predictable, and the value is immediately visible.
If you send weekly updates, start with /executive-update-generator. Run it alongside your normal update process for one week. Compare the outputs. Most PMs find that the skill-generated draft captures the structure and facts correctly, and they spend their editing time on framing and judgment — the high-value work.
If you're preparing for a board meeting, run /board-deck-generator a week before the deck is due. Use the output as your narrative skeleton. You'll arrive at the slide-building phase with a clear story instead of a blank deck.
If you just shipped a feature, run /release-notes-pro and /customer-announcement-writer. Having audience-specific versions of the same announcement is something most PM teams skip because of time. With skills, the marginal cost of a second version is five minutes of review.
If you haven't set up Claude Code yet, the setup guide walks through installation and context file creation step by step. For communication work, the investment in good context files pays back immediately — every communication skill is only as good as the product context it reads.
For the full picture of what's possible across all seven PM automation categories, the hub article covers everything from discovery to communication. And if you want to see where your team's communication maturity stands, the PM Team Maturity Assessment scores your team across nine dimensions — including Communication as a dedicated dimension.
Build this for your team → We set up and manage PM Operating Systems for product teams — communication infrastructure that makes every update, brief, and deck consistent across your team. See how it works →
The complete communication skill set — along with 70+ other PM skills across discovery, strategy, competitive intelligence, specs, planning, and data — is available in the PM Operating System.
About the Author
Ron Yang is the founder of mySecond — he builds and manages PM Operating Systems for product teams. Prior to mySecond, he led product at Aha! and is a product advisor to 25+ companies.