Meeting Prep Brief
Walk into the meeting already warm: who's in the room, what was promised last time, what you want out of this one, and the two questions worth asking — one page, read in the elevator. Locks the target meeting and the one-page criteria FIRST, then compiles from the calendar and the prior notes, so every claim in the brief traces to something real instead of memory. Use for meeting prep, 'prep me for the meeting', pre-meeting briefs, vendor and client syncs, and walking in warm.
Steps
Entry step: scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Scope the meetingplannerentry
target meeting, attendees from the record, history gathered
Show working prompt
Pick the meeting and gather everything before writing a word. Step 1: identify the target meeting — the one the owner names, or the next upcoming one worth prep — from calendar.json in the workspace or through the project's calendar capabilities when the calendar is wired as a live service, and pull its details: when, where, and exactly who is in the room. Step 2: gather the history — prior notes for this meeting or these people under notes/, and the open commitments made last time (who promised what, and whether it happened). Step 3: agree with the owner what they want out of this meeting — the one outcome that makes it a success. Step 4: write an acceptance-criteria checklist ('attendees listed from the calendar record, not from memory', 'every last-time commitment appears with its current status', 'the goal is stated in one sentence', 'at least two questions worth asking, ranked', 'one page — readable in the elevator'). Call write_task_note with the meeting + attendee count + checklist and write notes/scope.md. - Write the briefcopywriter
one page: room, goal, last time, agenda, the questions
Show working prompt
Write the one-page brief from what you gathered. Step 1: header — the meeting, when, and who is in the room, straight from the calendar details. Step 2: the goal — what the owner wants out of this one, in one sentence near the top. Step 3: last time — each commitment from the prior notes with its honest status: done, in motion, or silently dropped (the dropped ones are usually the real meeting). Step 4: the agenda as you would run it — short, ordered, loosely timed. Step 5: the questions — at least two worth asking, ranked, phrased ready to say out loud. Keep every claim traceable to the calendar or the notes; where the record is silent, say so rather than invent. One page. Write report.md and call write_task_note with the goal and the top question.
- Evaluatereviewer
Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
Show working prompt
Open report.md, the prior notes under notes/, and the calendar details and verify every criterion from notes/scope.md: every attendee in the brief matches the calendar record, every commitment listed traces to the prior notes with an honest status, the goal is one sentence, at least two ranked questions are present and phrased to ask aloud, nothing in the brief is invented — every claim has a source in the notes or the calendar — and it fits one page. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to brief. 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: "brief" })` 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. - 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.
- prep me for the meeting
- meeting prep brief
- get me ready for the meeting
- brief me before the meeting
- what do i need for this meeting
Source
View this craftbook on GitHub · MIT license