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.

Confirm your understanding before building the JSON.

---

Step 3: Choose Components and Narrative Order

The component sequence IS the story. Read references/components.md for the full component catalog, props schemas, and HTML patterns.

Always true:

• Open with hero — sets the company, label, and hero sentence.
• Close with highlights — narrative "so what" belongs last.
• Maximum one trend, one table, and one highlights per report.
• Keep total block count to 4–8.

Narrative intent drives the block order:

The hero sentence signals intent to the reader. Achievement heroes lead with a number and a direction. Problem heroes lead with a situation. Status heroes lead with a scope statement.

Component selection guide:

Hard rules:

• Never put a headline number in prose when kpi-row can show it larger.
• Never use table for 2–4 numbers — use kpi-row.
• kpi-row is not mandatory — omit it when the story is problem- or urgency-forward and metrics are supporting context, not the lead.

---

Step 4: Build and Validate the JSON Document

Construct the JSON object. Top-level structure:

report object (document metadata):

blocks array — ordered list of content blocks. Each block: type string + props object. See references/components.md for every component's full props schema.