Exec Summary
Turn the last substantive assistant message, or the user-provided source if one is provided, into a short decision-ready summary.
Goal
Help the user decide what to do next. Preserve only the information that affects understanding, risk, priority, or choice. Do not add new facts, analysis, or recommendations that were not supported by the source.
Style rules
- Use plain language.
- Be useful and short, but not tiny.
- Target 150–300 words unless the source is extremely small or the user asks for a different length.
- Put the bottom line first.
- Remove ornaments: no hype, no emojis, no decorative phrasing, no throat-clearing.
- Keep qualifiers when they matter, especially uncertainty, assumptions, constraints, risk, or validation status.
- Prefer concrete nouns and verbs over abstract summaries.
- Do not include process narration unless it affects the decision.
- Do not cite every detail. Include file names, commands, dates, metrics, or dependencies only when they change the decision.
Default format
Use this structure unless the user asks for another format:
**BLUF:** One or two sentences with the main conclusion and recommended direction.
**Important details**
- 3–5 bullets covering facts that matter for the decision.
**Trade-offs**
- 2–4 bullets comparing costs, risks, upside, and uncertainty.
**Options**
1. **Recommended:** The most sensible next move and why.
2. **Alternative:** A viable different path and when to choose it.
3. **Defer:** What happens if the user waits or does nothing, if relevant.
When the source is a coding-task result
Emphasize:
- what changed
- why it matters
- validation that actually ran, or that no validation ran
- known risks or incomplete work
- the next decision the user needs to make
When the source is an analysis or plan
Emphasize:
- the core finding or recommendation
- decision criteria
- meaningful alternatives
- risks and reversibility
- what information would change the recommendation
Compression guidance
Delete details that are only narrative, chronological, decorative, or obvious. Keep details that answer one of these questions:
- What is the main point?
- What changed or was learned?
- What choice does the user face?
- What are the risks or trade-offs?
- What should the user do next?
1---2name: exec-summary3description: Summarize the last substantive assistant message in plain language for decision-making: concise but not too short, bottom line up front, important details only, trade-offs, and practical options without ornaments.4---56# Exec Summary78Turn the last substantive assistant message, or the user-provided source if one is provided, into a short decision-ready summary.910## Goal1112Help the user decide what to do next. Preserve only the information that affects understanding, risk, priority, or choice. Do not add new facts, analysis, or recommendations that were not supported by the source.1314## Style rules1516- Use plain language.17- Be useful and short, but not tiny.18- Target 150–300 words unless the source is extremely small or the user asks for a different length.19- Put the bottom line first.20- Remove ornaments: no hype, no emojis, no decorative phrasing, no throat-clearing.21- Keep qualifiers when they matter, especially uncertainty, assumptions, constraints, risk, or validation status.22- Prefer concrete nouns and verbs over abstract summaries.23- Do not include process narration unless it affects the decision.24- Do not cite every detail. Include file names, commands, dates, metrics, or dependencies only when they change the decision.2526## Default format2728Use this structure unless the user asks for another format:2930```markdown31**BLUF:** One or two sentences with the main conclusion and recommended direction.3233**Important details**34- 3–5 bullets covering facts that matter for the decision.3536**Trade-offs**37- 2–4 bullets comparing costs, risks, upside, and uncertainty.3839**Options**401. **Recommended:** The most sensible next move and why.412. **Alternative:** A viable different path and when to choose it.423. **Defer:** What happens if the user waits or does nothing, if relevant.43```4445## When the source is a coding-task result4647Emphasize:4849- what changed50- why it matters51- validation that actually ran, or that no validation ran52- known risks or incomplete work53- the next decision the user needs to make5455## When the source is an analysis or plan5657Emphasize:5859- the core finding or recommendation60- decision criteria61- meaningful alternatives62- risks and reversibility63- what information would change the recommendation6465## Compression guidance6667Delete details that are only narrative, chronological, decorative, or obvious. Keep details that answer one of these questions:6869- What is the main point?70- What changed or was learned?71- What choice does the user face?72- What are the risks or trade-offs?73- What should the user do next?
bonkey