exec-report

Exec Report

Generates a complete, self-contained HTML report by (1) interviewing the user or parsing their data, (2) constructing and validating a JSON document, then (3) rendering that JSON into HTML using assets/report-template.html. The JSON is the authoritative source of truth; the HTML is fully determined by it.

---

Step 1: Determine the Data Source

Check what the user has already provided before asking anything:

• SharePoint lists: Call list_items on the relevant lists. Read all needed columns before proceeding.
• CSV or table pasted in chat: Parse all rows. Do not ask for data you already have.
• Verbal description only: Proceed to Step 2.

---

Step 2: Interview the User

If the data or intent is not fully clear, ask these questions in a single message — not one at a time:

1. Topic: What is this report about? (e.g., "Q2 pipeline health," "IT project status," "department spend overview")
2. Audience: Who is reading it? Exec team, department head, all-hands? This determines detail level.
3. Narrative intent: What is the shape of the story? Pick the closest match:
   • Achievement — "we hit a goal, here's how" (lead with the win: kpi-row + trend dominate)
   • Problem — "something needs attention, here's what" (lead with urgency: status-grid or table comes first)
   • Status — "here's where everything stands" (balanced overview: status-grid early, kpi-row supporting)
4. Headline message: What should the reader walk away knowing? This becomes the hero sentence — one sentence.
5. Sections wanted: Any specific sections — comparison to prior period, breakdown by category, status of open items, narrative highlights?
6. Palette: Warm paper (cream/terra-cotta), deep ink (dark/gold), clean white (white/green), or slate (gray/blue)? Default to warm paper if no preference.

If the user's prompt already signals narrative intent (e.g., "the headline is the gap," "lead with urgency," "show the wins"), skip question 3 — you already have the answer.