84 lines
2.2 KiB
Markdown
84 lines
2.2 KiB
Markdown
---
|
||
name: stakeholder-update
|
||
description: Produce concise stakeholder updates that summarize status, progress, risks, decisions, and next actions in a format leaders and cross-functional teams can scan quickly. Use this whenever users ask for a status update, progress update, weekly update, monthly update, leadership summary, project brief, 経営報告, or エスカレーション共有; use it for recurring project or business reporting, not for meeting minutes or one-page decision memos.
|
||
---
|
||
|
||
# Stakeholder Update
|
||
|
||
## Overview
|
||
|
||
Turn scattered project or business information into concise updates that help stakeholders understand status, risks, and decisions quickly.
|
||
|
||
This skill is for:
|
||
- Weekly or biweekly status updates
|
||
- Leadership summaries
|
||
- Cross-functional project updates
|
||
- Escalation-ready communication
|
||
- Alignment notes after major milestones
|
||
|
||
## Triggering Cues
|
||
|
||
Use this skill when user messages include:
|
||
|
||
- write a status update
|
||
- summarize progress for stakeholders
|
||
- weekly project update
|
||
- leadership summary
|
||
- project health update
|
||
- escalation note
|
||
|
||
## Input Requirements
|
||
|
||
Ask for or infer:
|
||
|
||
1. Current status and major progress points
|
||
2. Risks, blockers, or delays
|
||
3. Decisions needed
|
||
4. Upcoming milestones
|
||
5. Audience level (team / managers / executives)
|
||
|
||
## Output Format
|
||
|
||
Always output:
|
||
|
||
1. **Status Snapshot**
|
||
2. **Progress Since Last Update**
|
||
3. **Risks / Issues / Blockers**
|
||
4. **Decisions Needed**
|
||
5. **Next 1-2 Week Plan**
|
||
|
||
## Workflow
|
||
|
||
1. Identify the audience and information density needed.
|
||
2. Separate facts, risks, and asks.
|
||
3. Lead with status and business impact.
|
||
4. Make decision requests explicit.
|
||
5. End with the immediate plan and ownership where possible.
|
||
|
||
## Examples
|
||
|
||
### Example 1
|
||
Input:
|
||
- Summarize this week’s delivery progress for cross-functional leadership.
|
||
|
||
Output style:
|
||
- Executive-friendly
|
||
- Low noise, high signal
|
||
- Risks and decisions surfaced clearly
|
||
|
||
### Example 2
|
||
Input:
|
||
- We need an escalation-ready update because one dependency team is blocking launch.
|
||
|
||
Output style:
|
||
- Neutral and factual
|
||
- Clear blocker ownership
|
||
- Specific decision or support request
|
||
|
||
## Guidelines
|
||
|
||
- Keep updates skimmable.
|
||
- Avoid burying risks at the end.
|
||
- Distinguish facts from assumptions.
|
||
- Do not overstate progress or certainty.
|