report-writing

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: report-writing
description: This skill should be used when the user asks to "write a report", "executive summary", "research report format", "report structure", "present findings", "business writing", "analysis documentation", or needs guidance on structuring research outputs, executive communication, or professional report formatting.
version: 0.1.0
---

# Report Writing

## Overview

Report writing transforms research findings into clear, actionable documents for decision-makers. This skill covers best practices for structuring, writing, and visualizing market research outputs.

## Critical Rules

1. **ALWAYS start with the Executive Summary** — no report should open with methodology, background, or definitions. The first substantive section must state the bottom-line findings and recommendation.
2. **NEVER fabricate data** — if a number is not provided, say so explicitly. Present ranges when sources disagree. Use hedging language ("data suggests", "estimated") for uncertain claims.
3. **EVERY finding must have a "so what"** — orphan facts that don't connect to implications or recommendations waste the reader's time.
4. **ALWAYS use active voice** — passive voice obscures who did what. Write "Stripe captured 40% share" not "40% share was captured by Stripe".
5. **ALWAYS include at least one Mermaid diagram** — visualization is not optional. Use pie charts for composition, quadrant charts for positioning, state diagrams for scenarios.
6. **Recommendations MUST include What/Why/How/Risk** — vague recommendations ("consider expanding") are useless. Be specific and actionable.
7. **Preserve exact data from the user** — do not round, reinterpret, or omit numbers the user provides. Every data point given must appear in the output.
8. **Match report type to audience** — executive briefs for C-suite (1-2 pages), research summaries for VPs (3-5 pages), full reports for analysts (10-30 pages).

## Report Type Selection

When the user does not specify a report type, use this decision table:

| Signal in User Prompt | Default Report Type |
|----------------------|-------------------|
| "executive brief", "for the CEO", "quick summary" | Executive Brief |
| "research summary", "3-5 pages", "for VPs" | Research Summary |
| "full report", "comprehensive", "detailed", "include everything" | Full Report |
| "data pack", "supporting data", "appendix only" | Appendix/Data Pack |
| No clear signal | Research Summary (safest default) |

## Report Types

### Executive Brief (1-2 pages)
- Key findings only
- Single recommendation
- For: C-suite, board
- Time to read: 5 minutes

### Research Summary (3-5 pages)
- Main findings with evidence
- Multiple recommendations
- For: VPs, directors
- Time to read: 15 minutes

### Full Report (10-30 pages)
- Comprehensive analysis
- Detailed methodology
- For: Analysts, implementers
- Time to read: 30-60 minutes
- MUST include: Table of Contents, at least 6 major sections, Appendix with methodology and data sources. Include `quadrantChart` for competitive positioning only when a competitive dimension is present in the findings. Include `stateDiagram` for scenario analysis only when scenario or trend data is available

### Appendix/Data Pack
- Supporting data
- Detailed tables
- For: Deep dives
- Reference as needed

## Document Structure

### Executive Summary (Always First)

The Executive Summary is the most important section of any report. It must stand alone as a decision document — a reader who reads only the Executive Summary should know the key findings, the recommendation, and the primary risk.

**Length**: 1 paragraph to 1 page
**Content** (in this order):
1. Context (1 sentence — what was analyzed and why)
2. Key findings (3-5 bullets — the essential facts)
3. Primary recommendation (bold, specific, actionable)
4. Critical risk or caveat (the main thing that could go wrong)

**Rules**:
- NEVER open the Executive Summary with methodology ("We conducted..."). Open with the context or the most