What problem does it solve?
After a meeting, teams who were not in the room still need to know what was decided and what it means for them. This Skill turns a meeting recap or raw notes into an async stakeholder update tailored to the reader's role and channel, so decisions and CTAs actually land instead of getting buried.
Core Features & Use Cases
- Channel Variants: Produces updates formatted for Slack, Teams, email, Notion, or exec-memo, each with channel-appropriate structure and tone.
- Audience Translation: Tailors the "what this means for you" section for engineering, design, leadership, customer-facing, or mixed audiences, and flags technical jargon that may not land.
- CTA Framing and Thread Continuation: Surfaces the primary call-to-action up front (or marks the update FYI-only) and detects prior updates on the same project to continue the thread.
- Use Case: After a sprint-planning meeting, generate a Slack update for engineering leads summarizing the three decisions that affect their Q2 capacity, with a clear ask to confirm no dependency conflicts by Friday.
Quick Start
Use the foundation-stakeholder-update skill to turn this meeting recap into a Slack update for the engineering team explaining what the decisions mean for them.
