exec-summary

Name: exec-summary
Author: mvschwarz

56stars9forks

How to install exec-summary?

mvschwarz/openrig/exec-summary

$npx -y skills add mvschwarz/openrig --skill exec-summary

Installs into the current project.

Summary

Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

Files · 1

View on GitHub

SKILL.md

1	You 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
5	A 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
9	Before writing, silently gather all context from the feature folder:
10
11	1. requirements.md — acceptance criteria, business rules, scope, user stories
12	2. background.md — customer drivers, competitive context, regulatory considerations
13	3. validation.md — demand evidence, status quo, desperate user, narrowest wedge
14	4. supporting/mockup-ascii.md — visual mockups (pull 2-3 key screens)
15
16	## Output Structure
17
18	```markdown
19	---
20	title: "Executive Summary: [Feature Name]"
21	feature: [feature-folder-name]
22	status: [ready \| in-progress \| shipped]
23	jira: [ticket key]
24	updated: [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	[5-8 non-obvious business rules and design choices. Focus on surprising or counter-intuitive ones.]
46
47	## Visual Preview
48	[2-3 ASCII mockup screens from supporting/ — the key screens that tell the story.]
49
50	## What We're NOT Building
51	[5-8 key out-of-scope items with brief reason.]
52
53	## Dependencies & Sequencing
54	[What must ship first. Cross-feature dependencies. Prerequisites.]
55
56	## Success Metrics
57	[2-4 measurable outcomes. Mix of usage and business metrics.]
58
59	## FAQ
60
61	### For Sales
62	[2-3 questions. When available, what to tell prospects, competitive positioning.]
63
64	### For Leadership
65	[2-3 questions. Opportunity cost, strategic fit, risks.]
66
67	### For Engineering
68	[2-3 questions. Dependencies, known risks, what's deferred, data model implications.]
69	```
70
71	## Writing Guidelines
72
73	- Present tense throughout. Write as if the feature exists.
74	- Customer-readable language. A prospect should understand sections 1-5.
75	- Be specific, not vague. Name deals, dollar amounts, competitors.
76	- Key Decisions should surprise. Don't list obvious things.
77	- Mockups are curated. Pick the 2-3 that tell the story.
78	- FAQ answers should be direct. No hedging.
79	- Hard cap: 2 pages for core content. FAQ can be a third page.

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

exec-summary

56stars9forks

View on GitHub

How to install exec-summary?

mvschwarz/openrig/exec-summary

$npx -y skills add mvschwarz/openrig --skill exec-summary

Installs into the current project.

Summary

Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

Files · 1

View on GitHub

SKILL.md

1	You 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
5	A 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
9	Before writing, silently gather all context from the feature folder:
10
11	1. requirements.md — acceptance criteria, business rules, scope, user stories
12	2. background.md — customer drivers, competitive context, regulatory considerations
13	3. validation.md — demand evidence, status quo, desperate user, narrowest wedge
14	4. supporting/mockup-ascii.md — visual mockups (pull 2-3 key screens)
15
16	## Output Structure
17
18	```markdown
19	---
20	title: "Executive Summary: [Feature Name]"
21	feature: [feature-folder-name]
22	status: [ready \| in-progress \| shipped]
23	jira: [ticket key]
24	updated: [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	[5-8 non-obvious business rules and design choices. Focus on surprising or counter-intuitive ones.]
46
47	## Visual Preview
48	[2-3 ASCII mockup screens from supporting/ — the key screens that tell the story.]
49
50	## What We're NOT Building
51	[5-8 key out-of-scope items with brief reason.]
52
53	## Dependencies & Sequencing
54	[What must ship first. Cross-feature dependencies. Prerequisites.]
55
56	## Success Metrics
57	[2-4 measurable outcomes. Mix of usage and business metrics.]
58
59	## FAQ
60
61	### For Sales
62	[2-3 questions. When available, what to tell prospects, competitive positioning.]
63
64	### For Leadership
65	[2-3 questions. Opportunity cost, strategic fit, risks.]
66
67	### For Engineering
68	[2-3 questions. Dependencies, known risks, what's deferred, data model implications.]
69	```
70
71	## Writing Guidelines
72
73	- Present tense throughout. Write as if the feature exists.
74	- Customer-readable language. A prospect should understand sections 1-5.
75	- Be specific, not vague. Name deals, dollar amounts, competitors.
76	- Key Decisions should surprise. Don't list obvious things.
77	- Mockups are curated. Pick the 2-3 that tell the story.
78	- FAQ answers should be direct. No hedging.
79	- Hard cap: 2 pages for core content. FAQ can be a third page.

People who liked this also viewed

6 picks

Type