菜单
Draft stakeholder updates tailored to audience — executives, engineering, customers, or cross-functional partners. Use when writing weekly status updates, monthly reports, launch announcements, risk communications, or decision documentation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
新しいエージェントを雇用（作成・起動）するスキル。ディレクトリ作成、CLAUDE.md生成、スキルコピー、roster更新、tmux起動まで一貫して行う。
Generate a daily summary report of all team activities
Generate and update the team dashboard report (org/dashboard.md)
Capture and codify company-specific data knowledge — entity definitions, metric formulas, table schemas, and tribal knowledge. Use when onboarding to a new data environment, documenting institutional data knowledge, or building a data dictionary.
Profile and explore datasets to understand their shape, quality, and patterns before analysis. Use when encountering a new dataset, assessing data quality, discovering column distributions, identifying nulls and outliers, or deciding which dimensions to analyze.
QA an analysis before sharing with stakeholders — methodology checks, accuracy verification, and bias detection. Use when reviewing an analysis for errors, checking for survivorship bias, validating aggregation logic, or preparing documentation for reproducibility.
| name | stakeholder-comms |
| description | Draft stakeholder updates tailored to audience — executives, engineering, customers, or cross-functional partners. Use when writing weekly status updates, monthly reports, launch announcements, risk communications, or decision documentation. |
You are an expert at product management communications — status updates, stakeholder management, risk communication, decision documentation, and meeting facilitation.
Status: [Green / Yellow / Red]
TL;DR: [One sentence — the most important thing to know]
Progress:
- [Outcome achieved, tied to goal/OKR]
- [Milestone reached, with impact]
Risks:
- [Risk]: [Mitigation plan]. [Ask if needed].
Decisions needed:
- [Decision]: [Options with recommendation]. Need by [date].
Next milestones:
- [Milestone] — [Date]
Tips: Lead with the conclusion. Keep it under 200 words. Status color should reflect genuine assessment. Asks must be specific.
Shipped:
- [Feature/fix] — [Link]. [Impact if notable].
In progress:
- [Item] — [Owner]. [Expected completion]. [Blockers].
Decisions:
- [Decision made]: [Rationale].
- [Decision needed]: [Context]. [Options]. [Recommendation].
Priority changes:
- [What changed and why]
What's coming:
- [Feature/launch] — [Date]. [What this means for your team].
What we need from you:
- [Specific ask] — [Context]. By [date].
Open for input:
- [Topic we'd love feedback on]
Frame everything in terms of what the customer can now DO. No internal jargon. Be honest about timelines but do not overcommit.
Move to Yellow at the FIRST sign of risk, not when you are sure things are bad.
# [Decision Title]
## Status
[Proposed / Accepted / Deprecated / Superseded]
## Context
What situation requires a decision? What forces are at play?
## Decision
What did we decide? State clearly and directly.
## Consequences
Positive consequences, negative consequences/tradeoffs, what this enables or prevents.
## Alternatives Considered
What other options were evaluated? Why were they rejected?
Focus on blockers. Cancel if nothing to sync on.
Come with proposed priority order. Push back on overcommitment.
Create psychological safety. Focus on systems, not individuals. Limit to 1-3 action items. Follow up on previous retro items.
Demo the real product, not slides. Frame feedback collection with specific questions.