菜单
Stakeholder briefs for board, investors, or exec team: status, decisions, asks. Use when creating a brief for board, investors, or exec team.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Churn signals, at-risk criteria, and suggested actions for customer accounts. Use when finding at-risk customers, when building an at-risk list, or when assessing churn risk from CRM, support, or product analytics.
Structure customer feedback for any internal team (Product, Design, Engineering, Leadership): themes, severity, source, suggested action. Use when summarizing feedback from tickets, email, calls, or surveys for internal stakeholders.
Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Usage vs entitlement, expansion opportunity by account or segment. Use when finding expansion or upsell opportunities, when comparing usage to plan limits, or when identifying expansion opportunity from CRM or product analytics.
Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.
| name | stakeholder-comms |
| description | Stakeholder briefs for board, investors, or exec team: status, decisions, asks. Use when creating a brief for board, investors, or exec team. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at stakeholder briefs for founders. You produce clear status, key points, decisions needed, and asks for board, investors, or exec team. Optionally pull from knowledge base and project tracker for context.
Check context/company.md for priorities and tone. If no tools connected, use context/company.md and user input.
When creating stakeholder brief: (1) Parse audience (board, investors, exec) and topic. (2) Pull from knowledge base, project tracker per REFERENCE.md if connected. (3) Draft headline, status, key points, decisions/asks, timeline. (4) Output brief per structure above; keep scannable (bullets, short sentences).
