← All craftbooks

Board Meeting Deck

Documents and decksevalv1.0.0released 2026-06-05workflow: build-loop

Steps

Entry step: narrative. Each step names the specialist role it wants; the full working prompt is expandable.

1. Board narrativeplannerentry

   lock the standard board slide order + the KPIs + the asks

   Show working prompt

   Structure the board story before any design — boards expect a consistent shape. Step 1: gather inputs: the period's headline, the KPIs that matter (with current vs target vs prior), financial summary (revenue, burn, runway), progress against the goals set last meeting, key risks, and the specific ASKS/decisions you need from the board. Step 2: lay out the canonical order: (1) title + period, (2) executive summary / TL;DR, (3) KPI dashboard, (4) financials + runway, (5) progress against last quarter's goals, (6) key risks + mitigations, (7) asks/decisions needed, (8) appendix. Step 3: for each KPI decide current value, comparison, and status (on/off track). Step 4: write the explicit asks as decisions the board must make. Step 5: write an acceptance-criteria checklist ('opens with an executive summary slide', 'KPI dashboard shows current vs target/prior with status', 'financials include runway', 'progress slide references last quarter's goals', 'a dedicated asks/decisions slide states what is needed', 'one topic per slide'). Write the slide-by-slide outline + metrics + checklist via write_task_note AND to notes/narrative.md. No design or HTML yet.

2. Dashboard designdesigner

   dense, data-forward slide system with status colors

   Show working prompt

   Design a data-forward slide system suited to dense board content. Step 1: pick a restrained, serious palette with exact hex plus a clear status scale (on-track / at-risk / off-track colors used consistently). Step 2: define the grid: title + period in a header, a footer with slide number and confidentiality label, and a content zone that can hold a KPI grid or a metrics table without feeling cramped. Step 3: define slide archetypes: an executive-summary slide, a KPI dashboard (a grid of metric cards: label, big value, comparison, status dot), a financials slide (table + runway callout), a progress slide (goal -> status rows), a risks slide, and an asks slide that visually stands out. Step 4: ensure big numbers and statuses are scannable at a glance. Step 5: write a visual-criteria checklist ('consistent status colors throughout', 'KPI values are visually dominant', 'every slide has header period + footer slide number', 'asks slide visually distinct'). Write the slide-system spec + checklist via write_task_note AND to notes/design.md. No content yet.

3. Build the deckdeveloper

   implement index.html dashboard deck to the locked order + system

   Show working prompt

   Implement the board deck as a single self-contained index.html (inline CSS + minimal JS, no external assets). Step 1: create one full-viewport section per slide in the locked board order. Step 2: apply the design system exactly — palette hex, the status color scale used consistently, header with period and footer with slide number + confidentiality label on every slide. Step 3: render the KPI dashboard as a grid of metric cards (label, dominant value, vs target/prior, status dot) and the financials slide with a table + a runway callout. Step 4: render the progress slide as goal -> status rows and make the asks/decisions slide visually distinct so directors cannot miss what is needed. Step 5: wire arrow-key navigation and visible slide numbers. Drop the approved numbers/content in verbatim; do not invent metrics. On a loop-back, fix ONLY the named gaps. Write the deck path + slide count via write_task_note.

4. Evaluatereviewer

   Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.

   Show working prompt

   QA the board deck against the locked criteria. Step 1: open/render index.html and step through every slide with the arrow keys. Step 2: verify the board order (title -> exec summary -> KPI dashboard -> financials -> progress -> risks -> asks -> appendix). Step 3: check EACH acceptance criterion: opens with an executive summary, the KPI dashboard shows current vs target/prior with a consistent status color scale and dominant values, financials include runway, the progress slide references last quarter's goals, a dedicated asks/decisions slide clearly states what the board must decide and is visually distinct, every slide has the period header + slide-number footer, and there is one topic per slide. Step 4: confirm no metrics were invented beyond the outline. Write PASS/FAIL per criterion with the offending slide on any FAIL.
   
   Then route — this is the whole point of the loop:
   
   - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`.
   - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "build" })` to loop back. The builder fixes exactly those gaps.
   
   Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in.

5. Finishdeveloper

   All acceptance criteria met. Stamp a short summary and report DONE.

   Show working prompt

   Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.

Triggers

Phrases that suggest this craftbook to a crew.

• board deck
• board meeting slides
• board update deck
• quarterly board deck
• directors presentation
• board report deck

Source

View this craftbook on GitHub · MIT license