william-yeh Executive Summary Generator
Overview
Generates a senior-manager-ready executive summary from any report input, using a structured communication framework. Always includes gap analysis. Adapts to language, input format, and whether the source is already structured.
Input
Accept any of:
- Pasted text
- File path → read with Read tool
- URL → fetch with WebFetch tool
Output
- Format: Markdown
- Length: soft limit 500 繁體中文字 or semantic equivalent in English; adjustable on request
- Style: professional business without cliché
- Chinese: 台灣現代風格的繁體中文
- English: global English
- Sentence style (default): journalist — short, declarative sentences; one idea per sentence; no subordinate clauses where a full stop works better
- Sentence style (on request): standard prose — longer, flowing sentences permitted
- Language: auto-detect from input; explicit user instruction overrides
Framework Selection
Default — no framework specified:
- Analyze the report type and content
- Recommend the most suitable framework with a one-line rationale
- Confirm with user before generating
User pre-states a framework: skip steps 1–3, generate directly.
Frameworks
1. 現況與目標、解決方案、執行模式、預期效益、後續行動
Operational and project reports. Logical progression: where we are → where we want to be → how we get there → what we gain → what happens next.
2. SCQA
Narrative-first. Situation (background) → Complication (problem/tension) → Question (what must be answered) → Answer (recommendation). Best when the problem needs to be felt before the solution lands.
3. SCR+N
Concise variant of SCQA. Situation → Complication → Resolution + explicit Next Steps. Use when time is short and the action path is clear.
4. Pyramid Structure Storyline
Logic-driven. Lead with conclusion, support with arguments, each argument backed by evidence. Apply the quality filter: 具體可行（有問對問題）、有效果、符合經濟效益、可落地.
5. OBRAO (劉恭甫，《不懂這些，別想加薪》)
Decision-meeting focused. Five sections:
| Section | Content |
|---|---|
| O — Objective | What decision needs to be made; who are the decision-makers and stakeholders |
| B — Benefit | Connect to 四高三低: 提高顧客滿意度/效率/市場佔有率/利潤; 降低成本/風險/研發或上市時間 |
| R — Reason | Problem analysis with quantified evidence |
| A — Argument | Solution addressing 3 questions: 解決方案是什麼？投入多少資源產生多少效益？如何證明有效？ |
| O — Option | 2–3 options max, each with explicit pros and cons |
Always-On: Gap Analysis
Every output must end with:
## ⚠️ Gaps & Weaknesses
Flag any of:
- Missing data or unquantified claims
- Logical gaps in the argument
- Unsupported assumptions
- Sections where the source report is weak or absent
If the source report is solid, say so explicitly — do not fabricate issues to fill this section.
Auto-Detection: Already-Structured Input
If the input is already organized with clear sections or follows a recognizable framework:
- Note this to the user
- Provide two versions:
- Reframe — restructure content into the chosen framework (may reorder or reframe arguments)
- Distill — compress the existing structure as-is, preserving the original flow
Workflow
Input received
→ detect language
→ fetch content (if file or URL)
→ detect if already structured
→ framework: user specified? → generate directly
not specified? → recommend + confirm
→ generate summary (soft 500字/words limit)
→ append ⚠️ Gaps & Weaknesses section
Framework Selection Heuristics
| Report type | Recommended framework |
|---|---|
| Decision meeting / 決策會議 | OBRAO |
| Problem investigation | SCQA |
| Project update / status report | 現況與目標… |
| Policy recommendation | Pyramid |
| Quick brief / briefing note | SCR+N |