Individual skill
exec-summary
Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.
packages/daemon/specs/agents/shared/skills/pm/exec-summary/SKILL.md
Source commit 344815052870e4b1be2486350ba52a8d1c6afeb2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 8,739
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-harness Repository topic
- agent-orchestration Repository topic
- agent-skills Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- codex-cli Repository topic
- multi-agent Repository topic
- tmux Repository topic
- typescript Repository topic
- engineering Derived category
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,904 bytes
Read excerpt
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).
## What You Produce
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.
## Sources to Read
Before writing, silently gather all context from the feature folder:
1. **SPEC.md** — acceptance criteria, business rules, scope, user stories
2. **background.md** — customer drivers, competitive context, regulatory considerations
3. **validation.md** — demand evidence, status quo, desperate user, narrowest wedge
4. **supporting/mockup-ascii.md** — visual mockups (pull 2-3 key screens)