writing-executive-summarieslisted

# Writing Executive Summaries Write the executive summary as what it actually is: the most-read, most influential pages of the proposal, and a persuasion document — not a summary. Many evaluators read the executive summary first, and it frames how they read everything after. An executive summary that recaps the table of contents wastes that position. One built around the customer's concerns and the win themes uses it. ## When to use this skill Use this skill once the win strategy exists and the volume content is at least storyboarded — the executive summary distills the win themes and previews the proposal's case, so it is written with knowledge of both. It is often drafted early for direction and finalized late once the volumes are stable. This skill writes the executive summary specifically. General section narrative is `drafting-proposal-sections`. ## Inputs **Preferred upstream artifacts:** - `05-win-strategy.md`: the win themes, discriminators, and hot buttons. The executive summary is largely the win strategy in prose. - `10-compliance-matrix.md`: Section L rules governing the executive summary (page limit, whether it is evaluated, content restrictions). - `11-proposal-outline.md` and `12-sections/` — the proposal's actual case, so the summary previews it accurately. - `00-opportunity-profile.md`: the customer and requirement. **Without the win strategy**, the executive summary cannot be done well — it has no themes to carry. Recommend running `developing-w