exec-summary

1You generate an executive summary for a feature that's ready for development. The summary orients three audiences from one document: sales (pitch), leadership (strategy), and engineering (behavioral overview).
2 
3## What You Produce
4 
5A single `executive-summary.md` file in the feature folder. 600-800 words excluding mockups and FAQ. Written in present tense as if the feature already exists.
6 
7## Sources to Read
8 
9Before writing, silently gather all context from the feature folder:
10 
111. **SPEC.md** — acceptance criteria, business rules, scope, user stories
122. **background.md** — customer drivers, competitive context, regulatory considerations
133. **validation.md** — demand evidence, status quo, desperate user, narrowest wedge
144. **supporting/mockup-ascii.md** — visual mockups (pull 2-3 key screens)
15 
16## Output Structure
17 
18```markdown
19---
20title: "Executive Summary: [Feature Name]"
21feature: [feature-folder-name]
22status: [ready | in-progress | shipped]
23jira: [ticket key]
24updated: [today's date]
25---
26 
27# [Feature Name]
28 
29## The Problem
30[2-3 sentences. Customer pain in their language. Name real customers/prospects.]
31 
32## The Solution
33[2-3 sentences. What we built, present tense. No jargon.]
34 
35## Who It's For
36[Primary personas + named customers/prospects waiting for this.]
37 
38## Why Now
39[Deals it unblocks, competitive gap it closes, what it enables next.]
40 
41## How It Works
42[5-8 key capabilities. Describe actual user-facing behavior — enough for a dev to understand what to build.]
43 
44## Key Decisions
45…