← All craftbooks

Design the Invitations

Home and everyday lifeevalv1.0.0released 2026-06-05workflow: build-loop

Steps

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

1. Lock the factsceremoniemeesterentry

   fact checklist from the event record, look brief

   Show working prompt

   Lock the facts before any design. Step 1: read event.json from the workspace — the occasion, date, time, venue, host, and RSVP instructions — and guests.json for who the invitation must speak to. Step 2: confirm the look brief with the owner — the mood of the day, colors or motifs that matter, and anything the honoree would hate. Step 3: write the fact checklist: date, time, venue, and RSVP line exactly as the event record has them, character for character — the invitation may be creative about everything except these. Step 4: write an acceptance-criteria checklist ('every fact matches event.json exactly', 'the RSVP instruction is present and actionable — who to tell, how, by when', 'the file is print-ready — @page setup, honest margins, one sheet', 'the look fits the brief'). Call write_task_note with the occasion + the fact list + checklist and write notes/scope.md.

2. Design the invitationdesigner

   print-ready invitation with every fact copied from the record

   Show working prompt

   Design the invitation as one print-ready HTML file at invitations/invitation.html. Step 1: lay out the card — the occasion first, then the facts from the locked checklist, copied from event.json, never retyped from memory. Step 2: the RSVP line — who to tell, how, and by when, exactly as the record has it. Step 3: art direction per the brief — set type, color, and ornament with intent; where the look wants imagery, use the project's image capabilities or tasteful drawn ornament. Step 4: make it print-ready — an @page rule with size and margins, print styles, everything on one sheet. Step 5: proof the facts one final time against event.json before completing. Call write_task_note with the file path and the four facts as printed.

3. Evaluatereviewer

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

   Show working prompt

   Open invitations/invitation.html and event.json side by side and verify every criterion from notes/scope.md: the date, the time, the venue, and the RSVP instruction each match the event record exactly — read them character by character, this is the check the whole book exists for — the RSVP line is actionable, the file is print-ready with proper page setup on one sheet, and the look honors the brief. Write PASS/FAIL per fact and per criterion; on any mismatch, quote both versions and loop back to design.
   
   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: "design" })` 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.

4. 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.

• design the invitations
• make the party invites
• invitation for the party
• printable invitation
• invites for the celebration

Source

View this craftbook on GitHub · MIT license