executive-summary

Solid

Executive summary authoring discipline covering Pyramid Principle (Minto SCQ), one-page architecture, decision-enabling structure, audience-aware compression, and the never-bury-bad-news rule. Applies answer-first sequencing, cognitive-economy writing, and named-owner recommendation framing to all outputs. Distinct from `domains/sales/skills/proposal-strategist` (persuasion-to-close focus) and `domains/business-support/skills/analytics-reporter` (data-narrative focus). Use when: converting a lengthy analysis or briefing into a board-ready one-page summary; structuring a decision memo for C-suite consumption; compressing a multi-team status report for executive review; or authoring a risk or incident summary that must be readable in under three minutes.

AI & Automation 3 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Executive Summary ## Cardinal Rule An executive summary that requires the reader to read the supporting document is not a summary; the summary IS the deliverable. Every output produced under this skill must be independently interpretable — context, decision, recommendation, and risk communicated completely within the one-page boundary, without reference to appendices or source material for the reader to reach a conclusion. All outputs are subject to the two-pass review gate (ADR-058). ## Fail-Fast Rule Stop and return a structured failure when any of the following is true: - No decision or action is identified; the requester cannot articulate what a reader must decide or do after reading. - The source material contains unresolved contradictions in key figures or scope that would require the reader to adjudicate ambiguity. - The audience tier is unspecified and cannot be inferred from context, making compression level undefined. - The one-page ceiling would be breached even with maximum compression, and no secondary format (two-page exception) has been authorised. - Risk or bad-news content is present in the source but the requester has instructed that it be omitted or minimised. Never produce a summary over an unresolved factual contradiction. Never omit material risk at requester direction. ## When to Apply Apply when: converting a detailed analysis, audit, or status report into a board-ready one-page summary; drafting a decision memo for a C-suite reader...

Details

Author
Canhada-Labs
Repository
Canhada-Labs/ceo-orchestration
Created
4 weeks ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

consulting-writing

Management-consulting writing craft — McKinsey SCR (Situation·Complication·Resolution), Minto Pyramid/MECE, BCG bold-bullet executive summary, so-what upfront, numeric precision, Forrester Landscape. Use when writing or reviewing an executive summary for decision-makers or a roll-up/landscape overview, or when a conclusion-first compressed structure, MECE completeness, or bold-bullet summary is needed.

67 Updated yesterday
alfadur7
AI & Automation Listed

exec-briefing

Brief executives with the answer first, the whole thing on one page, risks paired with the decision you need, and no surprises. Use when you must get a decision or an update in front of leadership who have five minutes and no context.

4 Updated today
Amey-Thakur
AI & Automation Solid

constructive-thinking

Compress chaotic information into a leader-ready structure before output. ALWAYS use when the user is preparing to brief a senior leader, present a technical proposal, write a one-pager, or otherwise turn scattered facts and feelings into Frame → Crux → Nodes → Tilt + Reasoning that fits in 3–5 minutes of reading. Trigger phrases include "向领导汇报", "做技术方案 presentation", "整理思路", "report up", "brief the boss", "summarize for leadership", "executive briefing", "one-pager". NOT for writing the final polished document (use tech-doc-writer), NOT for decomposing tasks into implementation steps (use writing-plans), NOT for incident root-cause analysis (use incident-postmortem), NOT for aggregating research with citations (use deep-research).

27 Updated yesterday
johnqtcg