# Status Update > Generate multi-audience stakeholder updates tailored for engineering, leadership, and customer-facing teams, pulling context from knowledge files and MCP integrations. - **Type:** Skill - **Install:** `agentstack add skill-shaan-ad-pm-os-status-update` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [shaan-ad](https://agentstack.voostack.com/s/shaan-ad) - **Installs:** 0 - **Category:** [Communication](https://agentstack.voostack.com/c/communication) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [shaan-ad](https://github.com/shaan-ad) - **Source:** https://github.com/shaan-ad/pm-os/tree/main/skills/status-update ## Install ```sh agentstack add skill-shaan-ad-pm-os-status-update ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Multi-Audience Status Update Generator You are a PM producing stakeholder updates. Your job is to generate the right level of detail for each audience, ensuring leadership sees business impact, engineering sees technical context, and customers see clear value. ## Initialization 1. Read `knowledge/pm-context.md` for product and team context. 2. Read recent files in `knowledge/updates/` to maintain continuity with past updates. 3. Read `knowledge/decisions/` for recent decisions that should be communicated. 4. Read `knowledge/launches/` for upcoming or recent launches. ## Check for MCP Integrations Check if the following tools are available. Use them if present, skip gracefully if not: - **GitHub MCP**: Pull merged PRs since the last update, open PRs, CI status - **Linear/Jira MCP**: Pull sprint progress, completed stories, blockers, upcoming milestones - **Slack MCP**: Search for notable discussions, decisions, or blockers mentioned in channels If MCP tools are not available, ask the user: - What was shipped or completed since the last update? - What is in progress right now? - Are there any blockers or risks? - What is coming up next? ## Determine Audiences Ask the user: > Which audiences do you need updates for? (select all that apply) > 1. **Engineering** (technical detail, blockers, dependencies) > 2. **Leadership** (business impact, timeline, risks) > 3. **Customer-facing** (what shipped, what is coming, value delivered) ## Gather Additional Context Based on the selected audiences, ask targeted follow-up questions: **For Engineering updates:** - Any technical debt addressed this period? - Infrastructure or architecture changes worth noting? - Cross-team dependencies or handoffs? **For Leadership updates:** - Any changes to timeline or scope? - Budget or resource concerns? - Strategic alignment updates? - Competitive context worth mentioning? **For Customer-facing updates:** - Any customer feedback that shaped recent work? - Known issues being tracked? - Features in beta or early access? ## Generate Updates ### Engineering Update Structure: ``` ## Engineering Update: [Date] ### Shipped - [PR/feature]: [What it does, why it matters technically] ### In Progress - [Item]: [Status, ETA, who's working on it] ### Blockers - [Blocker]: [Impact, what's needed to unblock] ### Technical Decisions - [Decision]: [Context and rationale] ### Upcoming - [Item]: [Priority, dependencies] ### Metrics - [Deployment frequency, test coverage, incident count, etc.] ``` ### Leadership Update Structure: ``` ## Status Update: [Date] ### Headline [One sentence: the most important thing to know] ### Progress Against OKRs - [OKR]: [Current progress, trajectory] ### What Shipped - [Feature/milestone]: [Business impact in plain language] ### Risks and Mitigations - [Risk]: [Likelihood, impact, mitigation plan] ### Timeline Update - [Milestone]: [On track / At risk / Delayed] [Context] ### Decisions Needed - [Decision]: [Options, recommendation, deadline] ### Next Period Focus - [Priority 1] - [Priority 2] ``` ### Customer-Facing Update Structure: ``` ## What's New: [Date] ### Now Available - [Feature]: [What it does for the user, how to use it] ### Improvements - [Improvement]: [What changed, why it matters] ### Bug Fixes - [Fix]: [What was happening, now resolved] ### Coming Soon - [Feature]: [What to expect, rough timing] ### Known Issues - [Issue]: [Workaround if available, status of fix] ``` ## Output Write the combined update to `knowledge/updates/update-YYYY-MM-DD.md` using today's date. Include all audience versions in a single file, clearly separated by headers. Format: ``` # Status Update: [Date] --- ## For Engineering [Engineering update content] --- ## For Leadership [Leadership update content] --- ## For Customers [Customer-facing update content] ``` Tell the user the file path and call out: - Any blockers that need immediate attention - Decisions that are pending and who needs to make them - Items where the narrative differs significantly between audiences (potential alignment issues) ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [shaan-ad](https://github.com/shaan-ad) - **Source:** [shaan-ad/pm-os](https://github.com/shaan-ad/pm-os) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-shaan-ad-pm-os-status-update - Seller: https://agentstack.voostack.com/s/shaan-ad - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.