executive-presentation
Guides Communications Lead through designing and building C-level strategy presentations and decision decks. Uses Pyramid Principle structure, "So What?" message extraction, and one-page summary design. The business case section requires inputs from all three prerequisite skills.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- executive-presentation
- owner
- communications-lead
- scope
- co-consult
- inputs
- [ "complexity-grades", "business-case", "readiness-scores" ]
- status
- active
- outputs
- [ "executive-deck" ]
- version
- 1.0.1
- metadata
- { "type": "process", "triggers": [ "executive presentation", "executive deck", "C-level presentation", "decision deck", "strategy deck", "board presentation" ] }
- capability
- consulting-executive-presentation
- relates_to
- [ { "type": "composes_with", "skill": "technical-feasibility" }, { "type": "composes_with", "skill": "org-readiness-assessment" }, { "type": "composes_with", "skill": "financial-modeling" }, { "type": "composes_with", "skill": "narrative-framework" }, { "type": "composes_with", "skill": "consulting-report-writing" } ]
- description
- Guides Communications Lead through designing and building C-level strategy presentations and decision decks. Uses Pyramid Principle structure, "So What?" message extraction, and one-page summary design. The business case section requires inputs from all three prerequisite skills.
- last_reviewed
- 1791417600000
- prerequisites
- technical-feasibility, org-readiness-assessment, financial-modeling
- catalog-parity
- skip
03 SKILL.md 正文
Context
Use in Phase 3 when producing the primary client-facing presentation. Prerequisites (technical-feasibility, org-readiness-assessment, financial-modeling) must be complete before this skill is invoked.
When to Use
Invoke this skill when the Communications Lead is ready to design and build the executive strategy deck for C-level stakeholders. All three prerequisite skill outputs must be available before execution begins.
Execution Steps
- Confirm Prerequisites: Verify outputs from technical-feasibility, org-readiness-assessment, and financial-modeling are available
- Define the Decision: What single decision must the executive audience make after this presentation?
- Pyramid Principle Structure: SCQA framework
- Situation: What is the current context the audience already knows?
- Complication: What has changed or is threatening?
- Question: What does this situation force us to ask?
- Answer: The recommendation (stated upfront, not at the end)
- Slide Architecture (standard executive deck):
- Title slide + Agenda (1 slide)
- Executive Summary / Recommendation (1-2 slides) — written last
- Context and Problem (2-3 slides)
- Analysis and Findings (3-5 slides, sourced from insight-synthesis)
- Business Case (2-3 slides, sourced from financial-modeling + technical-feasibility + org-readiness-assessment):
- Investment summary
- Expected returns (NPV/IRR)
- Key risks and mitigations
- Change management cost summary
- Recommended Path Forward (2-3 slides)
- Next Steps and Decision Request (1 slide)
- One-Page Summary Design: Distill entire presentation into 1 page: Situation (2 sentences), Recommendation (1 sentence), Business Case (3 bullets), Next Step (1 action)
- Executive Language Check: No jargon, every number has context, every slide has one message, no slide exceeds 5 bullet points
Output Format
- Slide deck (outline with: slide title, key message per slide, supporting evidence, visual recommendation)
- One-Page Executive Summary (standalone)
- Speaker notes for key slides
Save Output To: See Output Destination Mapping in
docs/co-consult.context.mdfor destination folder and naming convention. Create the folder if it does not exist. Do not hard-code output paths.
Related Skills
- narrative-framework
- consulting-report-writing
- financial-modeling
- insight-synthesis
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.