data-narrative-builder

name	data-narrative-builder
description	Transform analytical findings into a compelling, story-driven presentation or document. Activate when data exists but the story is unclear, when a presentation feels like a "data dump", or when you need to make findings memorable and actionable for a specific audience.

When to use

• A presentation exists but feels like a data dump rather than a story
• Findings are clear but the team struggles to communicate them compellingly
• A senior audience won't engage with a 20-slide deck (5 slides or fewer needed)
• Data must support a specific decision, and emotional resonance matters
• A recurring report needs to be restructured around a narrative

Process

1. Identify the central message — define the single most important insight the presentation must land; if you have multiple equally important messages, you need multiple presentations
2. Choose the narrative framework — select the structure: Situation–Complication–Resolution (most common for problem/solution), What–So What–Now What (for findings briefings), or Before–After–Bridge (for change stories). See references/narrative_frameworks.md.
3. Map the emotional arc — define how you want the audience to feel at each stage: start with comfort (shared context), build tension (the problem or surprising finding), resolve with confidence (the clear path forward)
4. Draft with data — apply pyramid principle (conclusion first in each section); round numbers for recall; humanise impact with concrete examples (e.g. "equivalent to 3,000 users leaving every month")
5. Assign visuals — for each narrative beat, select one chart that reinforces the story; see references/data_writing_guide.md for pairing text with visuals
6. Craft the opening and closing — opening must capture attention in under 10 seconds (a striking number, a counterintuitive finding, or a direct question); closing must specify a concrete call to action with a decision owner and deadline

Inputs the skill needs

• Required: the central insight or finding to communicate
• Required: audience profile — role, priorities, what they already know
• Required: the decision or action the narrative should drive
• Required: the data and charts that support the story (prepared separately)
• Optional: format constraints (slides, doc, email, video) and time limit

Output

• references/narrative_frameworks.md — Situation–Complication–Resolution and other patterns with examples
• references/data_writing_guide.md — pyramid principle, number formatting, humanising data
• assets/narrative_template.md — fill-in-the-blank story structure with placeholders for data and charts