florianbonnet14/ThePowerOfAnalytics_ClaudeSkills / executive-summary-writer
executive-summary-writer
VerifiedTransform analysis findings into clear, actionable executive summaries using the MAIN framework (Motive, Answer, Impact, Next steps) and Pyramidal Principle. Use when completing any analysis that needs stakeholder buy-in, preparing for leadership meetings, documenting investigation findings, writing business reviews, creating post-mortems, proposing initiatives based on data, or communicating insights to executives.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.6 KB |
| assets/executive-summary-template.md | markdown | 1.2 KB |
| executive-summary-writer-tutorial.md | markdown | 1.5 KB |
| references/examples.md | markdown | 13.2 KB |
| references/main-framework.md | markdown | 9.8 KB |
| references/templates.md | markdown | 8.3 KB |
references/templates.md
View on GitHub# Executive Summary Templates
## Template 1: Investigation Summary
Use for: Root cause analyses, problem investigations, incident reviews
```markdown
# [Problem/Opportunity Name] - Analysis Summary
## Executive Summary
### Motive
[2-3 sentences: What happened? Why did we investigate? Who's affected?]
### Answer
[3-4 sentences: What we found. What we recommend. Expected outcome.]
### Impact
[3-4 sentences: Quantified business impact. Upside if acted upon.
Downside if not. Timeline and confidence.]
### Next Steps
1. [Specific action] - Owner: [Name] - ETA: [Date]
2. [Specific action] - Owner: [Name] - ETA: [Date]
3. [Specific action] - Owner: [Name] - ETA: [Date]
4. [Review/decision gate] - Owner: [Name] - ETA: [Date]
---
## Supporting Analysis
### Key Finding #1: [Title]
[1-2 paragraphs]
[Supporting chart/data]
### Key Finding #2: [Title]
[1-2 paragraphs]
[Supporting chart/data]
### Key Finding #3: [Title]
[1-2 paragraphs]
[Supporting chart/data]
---
## Appendix
### Methodology
[How analysis was conducted]
### Alternative Hypotheses Tested
[What else we considered and why we ruled it out]
### Additional Data
[Supporting tables, charts, etc.]
```
---
## Template 2: Weekly Business Review
Use for: Regular performance reviews, weekly updates, status reports
```markdown
# [Team/Product Name] - Weekly Business Review
Week of [Date]
## Executive Summary
### Performance Overview
[2-3 sentences on overall performance vs. targets this week]
### Key Changes This Week
1. [Most important change and why it happened]
2. [Second most important change and why]
3. [Third most important change and why]
### Actions Required
1. [Action needed] - Owner: [Name] - ETA: [Date]
2. [Action needed] - Owner: [Name] - ETA: [Date]
---
## Detailed Metrics
### North Star Metric: [Metric Name]
- Current: [Value]
- WoW: [+/-X%]
- MoM: [+/-X%]
- vs Target: [XX% of target] π΄/π‘/π’
- Analysis: [Why it changed]
### Level 1 KPI: [Driver Name]
[Same format as above]
### Level 1 KPI: [Driver Name]
[Same format as above]
---
## Looking Ahead
### Next Week Expectations
[What we expect to happen based on current initiatives]
### Risks to Watch
[Potential issues that could emerge]
### Opportunities to Capture
[Positive trends to leverage]
```
---
## Template 3: Proposal/Initiative
Use for: New feature proposals, strategic initiatives, investment requests
```markdown
# Proposal: [Initiative Name]
## Executive Summary
### Opportunity
[Why this matters now. What problem it solves. Context.]
### Proposal
[What we're proposing. How it works. Why this approach.]
### Expected Impact
[Quantified benefits. Timeline. Confidence level. Risks.]
### Required Investment
[Resources needed: time, money, people]
### Next Steps to Approve
1. [Decision/approval needed] - Owner: [Name] - ETA: [Date]
2. [Resource allocation] - Owner: [Name] - ETA: [Date]
3. [Launch preparation] - Owner: [Name] - ETA: [Date]
---
## Detailed Proposal
### Problem Statement
[Comprehensive explanation of issue/opportunity]
### Proposed Solution
[Detailed description of what we'll build/do]
### Success Metrics
[How we'll measure if this works]
### Implementation Plan
[Phased rollout approach]
### Risk Mitigation
[What could go wrong and how we'll handle it]
---
## Appendix
### Market Research
[Supporting customer data]
### Competitive Analysis
[What others are doing]
### Technical Feasibility
[Engineering assessment]
### Financial Model
[Detailed ROI calculations]
```
---
## Template 4: Post-Mortem
Use for: Incident reviews, outage analyses, failure investigations
```markdown
# Post-Mortem: [Issue Name]
## Executive Summary
### What Happened
[Brief description of the issue and its impact]
### Root Cause
[One sentence: the true root cause]
### Impact
[Quantified customer and business impact]
### Prevention Plan
1. [Immediate fix] - Owner: [Name] - Status: [Done/In Progress]
2. [Short-term improvement] - Owner: [Name] - ETA: [Date]
3. [Long-term systematic change] - Owner: [Name] - ETA: [Date]
---
## Detailed Timeline
| Time | Event |
|------|-------|
| [Time] | Issue first occurred |
| [Time] | Issue first detected |
| [Time] | Investigation started |
| [Time] | Root cause identified |
| [Time] | Fix implemented |
| [Time] | Issue resolved |
**Total Duration:** [X hours/days]
---
## Root Cause Analysis (5 Whys)
1. Why did [issue occur]? β [Answer]
2. Why did [answer 1]? β [Answer]
3. Why did [answer 2]? β [Answer]
4. Why did [answer 3]? β [Answer]
5. Why did [answer 4]? β [Root cause]
---
## Impact Assessment
### Customer Impact
[How many customers affected, how severely]
### Business Impact
[Revenue, reputation, operational impact]
### Team Impact
[Hours spent, morale effect]
---
## What Went Well
- [Thing that helped]
- [Thing that helped]
## What Could Be Improved
- [Thing to fix]
- [Thing to fix]
---
## Action Items
### Immediate (Done)
- [β] [Action taken]
- [β] [Action taken]
### Short-term (1-4 weeks)
- [ ] [Prevention measure] - Owner: [Name] - ETA: [Date]
- [ ] [Monitoring improvement] - Owner: [Name] - ETA: [Date]
### Long-term (1-3 months)
- [ ] [Systematic change] - Owner: [Name] - ETA: [Date]
- [ ] [Process improvement] - Owner: [Name] - ETA: [Date]
```
---
## Template 5: Experiment/Test Results
Use for: A/B test results, pilot program outcomes, MVP evaluations
```markdown
# [Experiment Name] - Results Summary
## Executive Summary
### Test Overview
[What we tested, why, and for how long]
### Results
[Key metric changes with statistical significance]
### Recommendation
[Ship it / iterate / kill it, and why]
### Next Steps
1. [Action] - Owner: [Name] - ETA: [Date]
2. [Action] - Owner: [Name] - ETA: [Date]
---
## Test Details
### Hypothesis
[What we expected to happen and why]
### Methodology
- Sample size: [N]
- Duration: [X days]
- Split: [Control X% / Variant Y%]
- Primary metric: [Metric name]
### Results Summary
| Metric | Control | Variant | Change | P-value |
|--------|---------|---------|--------|---------|
| [Primary] | X% | Y% | +/-Z% | <0.05 |
| [Secondary] | X% | Y% | +/-Z% | <0.05 |
---
## Analysis
### What Worked
[Positive findings with supporting data]
### What Didn't Work
[Negative findings or surprises]
### Segment Insights
[How different user segments responded]
---
## Recommendation Details
### If Ship:
[Implementation plan, rollout schedule, monitoring plan]
### If Iterate:
[What to change, why, timeline for retest]
### If Kill:
[Alternative approaches to consider]
```
---
## Template 6: Quarterly Business Review (QBR)
Use for: Quarterly reviews, board updates, investor reports
```markdown
# Q[X] [Year] Business Review - [Company/Team Name]
## Executive Summary
### Quarter Highlights
[Top 3 achievements or changes this quarter]
### Performance vs. Goals
[Overall assessment: on track / ahead / behind]
### Key Priorities for Next Quarter
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
---
## Performance Dashboard
### Revenue/Growth
- Actual: $[X]
- vs Target: [X%]
- vs Last Quarter: [+/-X%]
- Analysis: [Brief explanation]
### Customer Metrics
- New Customers: [X]
- Churn: [Y%]
- Net Growth: [X]
- Analysis: [Brief explanation]
### Product Metrics
- [Key metric 1]: [Value and trend]
- [Key metric 2]: [Value and trend]
- [Key metric 3]: [Value and trend]
---
## Strategic Initiatives Update
### Initiative 1: [Name]
- Status: [On track / At risk / Complete]
- Progress: [What was accomplished]
- Next steps: [What's coming]
### Initiative 2: [Name]
[Same format]
### Initiative 3: [Name]
[Same format]
---
## Next Quarter Plan
### Goals
1. [Goal 1 with target metric]
2. [Goal 2 with target metric]
3. [Goal 3 with target metric]
### Key Initiatives
[Major projects planned]
### Resource Requirements
[What's needed to succeed]
### Risks & Mitigation
[Potential obstacles and plans to address]
```
---
## Quick Reference: When to Use Each Template
| Template | Use When... | Key Focus |
|----------|-------------|-----------|
| Investigation | Something went wrong or changed unexpectedly | Root cause + fix |
| Weekly Review | Regular performance tracking | Trends + actions |
| Proposal | Pitching a new idea or initiative | Opportunity + ROI |
| Post-Mortem | Learning from incidents/failures | Prevention + learning |
| Experiment | Reporting test/pilot results | Data + decision |
| QBR | Quarterly or board reviews | Big picture + strategy |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |