executive-summary
Executive Summary Skill
Writes executive summaries that busy decision-makers actually read — front-loaded with conclusions, structured for skimming, ruthless about what to include.
Required Inputs
- Source document or topic (paste or describe)
- Audience (CEO / board / investor / minister / client / committee)
- Decision or action needed (what should the reader do after reading?)
- Length limit (1 page / 2 pages / 500 words)
- Format (formal report / slide / email / briefing paper)
Core Principle
An executive summary is NOT a summary of the document. It is a standalone document that:
- States the conclusion upfront — not at the end
- Contains only what the reader needs to make a decision
- Can be understood without reading anything else
- Recommends a specific action
Output Structure
[Title]
Executive Summary Prepared for: [Audience] | Date: [Date] | Author: [Name]
Bottom line up front: [The most important thing. The recommendation or finding. 2-3 sentences. A reader who only reads this should know what you are asking or telling them.]
Background (why this matters): [2-3 sentences. Minimum context to understand the bottom line. Not the history — just what the reader needs now.]
Key findings / analysis:
- [Finding 1]: [One sentence — specific and evidence-based]
- [Finding 2]: [One sentence]
- [Finding 3]: [One sentence]
Options considered: (include only if a decision is being presented)
| Option | Benefit | Risk | Recommendation |
|---|---|---|---|
| [Option A] | [Benefit] | [Risk] | Recommended |
| [Option B] | [Benefit] | [Risk] | Not recommended |
Recommendation: [Specific. "We recommend [action] because [reason]. This will [outcome]." Not "we suggest consideration of options."]
Immediate next steps:
- [Action 1 — specific, with owner and date]
- [Action 2]
Risks of inaction: [What happens if the reader does nothing]
Full report: [Reference to where the full document can be found]
Adapting for Different Audiences
CEO/MD: Lead with financial or strategic impact. 1 page. Make the decision binary. Ask in sentence one. Board: Lead with governance or risk. Frame against organisational objectives. State specifically what you need from them. Investor: Lead with return or opportunity. Specific numbers. 1 page. Anticipate "why now." Minister/senior public sector: Lead with public benefit or policy alignment. Include cost-benefit framing. Client: Lead with their problem. Show you understand before presenting recommendation.
Quality Checks
- Bottom line in first 3 sentences
- Standalone — no need to read full document
- Recommendation is specific
- Fits length limit
- Written for audience priorities not author priorities
- Next steps have owners and dates
Example Trigger Phrases
- "Write an executive summary of this report: [paste]"
- "Summarise this document for the board: [paste]"
- "Create a one-pager from this proposal for the CEO"
- "Turn these findings into an exec summary"
More from mohitagw15856/pm-claude-skills
user-research-synthesis
Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps.
26prd-template
Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.
20stakeholder-update
Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
19competitive-analysis
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations.
18meeting-notes
Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.
17financial-due-diligence
Generate a financial due diligence checklist and analysis framework for any investment, acquisition, or partnership. Use when asked for a due diligence checklist, M&A financial review, investment analysis framework, or vendor financial assessment. Produces a document request list, key analytical questions, red flags checklist, and a summarised financial health assessment.
15