summary-report

name	summary-report
description	Generate structured summary reports from data, documents, meetings, or any content. Use when the user asks to create a summary, report, recap, briefing, or overview of information. Triggers include: summarize, create a report, give me a summary, recap, briefing, overview, key findings, or any request to condense information into a structured format.

Summary Report

Generate concise, well-structured summary reports tailored to the content type and audience.

Workflow

1. Identify the source material — Determine what needs summarizing (data, text, meeting notes, code, etc.)
2. Determine the audience and purpose — Executive, technical, general, or specific stakeholder
3. Select the appropriate template — Use one of the templates below or adapt as needed
4. Extract key points — Focus on findings, decisions, actions, and metrics
5. Generate the report — Follow the chosen template structure

Report Templates

Executive Summary

# [Title]

## Overview
One-paragraph high-level summary of the subject.

## Key Findings
- Finding 1 with supporting metric or evidence
- Finding 2 with supporting metric or evidence
- Finding 3 with supporting metric or evidence

## Recommendations
1. Actionable recommendation with priority level
2. Actionable recommendation with priority level

## Next Steps
- [ ] Specific action item with owner (if known)
- [ ] Specific action item with owner (if known)

Meeting Recap

# Meeting: [Title] — [Date]

## Attendees
- [List of participants]

## Agenda Items Discussed
1. Topic 1 — brief summary of discussion
2. Topic 2 — brief summary of discussion

## Decisions Made
- Decision 1 with context
- Decision 2 with context

## Action Items
| # | Task | Owner | Deadline |
|---|------|-------|----------|
| 1 | ...  | ...   | ...      |

## Next Meeting
- Date/Time: [if scheduled]
- Topics: [if pre-defined]

Data Analysis Summary

# [Analysis Title]

## Objective
What question or problem this analysis addresses.

## Data Sources
- Source 1: description and date range
- Source 2: description and date range

## Key Metrics
| Metric | Value | Change |
|--------|-------|--------|
| ...    | ...   | ...    |

## Insights
1. Insight with data-backed explanation
2. Insight with data-backed explanation

## Conclusions
Brief summary of what the data indicates.

Technical Summary

# [Component/System] Summary

## Context
Brief description of the system, component, or issue.

## Current State
- Architecture or current implementation overview
- Key technical details

## Issues / Findings
1. Issue with severity and impact
2. Issue with severity and impact

## Recommendations
- Technical recommendation with rationale
- Technical recommendation with rationale

## References
- Links to relevant code, docs, or tickets

Guidelines

• Be concise — Prioritize signal over noise; omit filler
• Use data — Support claims with numbers, dates, or evidence when available
• Structure for scanning — Use headings, bullet points, and tables
• Adapt tone — Match formality to audience (executive vs. technical)
• Flag uncertainty — Clearly mark assumptions or incomplete information
• Include timestamps — For time-sensitive reports, note when data was captured

Output Formats

Default output is Markdown. Adapt to other formats on request:

• Plain text for email
• JSON for programmatic consumption
• HTML for web embedding