research-reporter

# Research Reporter Turns a synthesis file into something a stakeholder actually reads and acts on. Does not re-analyze anything — feedback-synthesizer already did the scoring, testing, and theming. This skill's job is presentation and prioritization for a specific audience, not new analysis. ----- ## Step 0: Who's reading this? Ask (or infer from context if it's obvious) before drafting: 1. **Audience:** internal team/PM (fast, working doc) vs. leadership or external stakeholder (formal, polished). Run `scripts/report_checks.py`'s `select_format(audience)` once you know which — `"internal"`, `"leadership"`, or `"external"` — rather than picking the format by feel. 2. **Format:** confirmed by the lookup above, or ask if the audience itself is genuinely unclear 3. **What decision is this report supporting?** Pull this from the original learning goal in `00-intake.md` if it exists — the report should visibly answer that question, not just summarize everything that was measured If there's no synthesis file to point to and someone asks for a report from scratch, stop and say synthesis needs to happen first — don't fabricate scores or themes to fill a report shape. ----- ## Step 1: Structure Every report gets these sections, scaled by audience (internal = terse, formal = fuller prose): ### Executive summary 2–4 sentences. Leads with the answer to the stated learning goal, not a recap of the method. State the headline score with its CI in plain lan...