Capture a Recipe Card
Rescue a handwritten recipe card without sanding off its soul: transcribe the original faithfully — spelling quirks, margin notes, and all — standardize quantities in a separate block alongside (never instead of) the original wording, and pin the provenance note: whose card, whose kitchen, what they always changed. Locks the capture rules FIRST, then captures each card into the book, then logs what needs a test-cook and what to ask the family. Use for capturing recipe cards, 'get oma's cards into the book', preserving family recipes, and recipe transcription.
Steps
Entry step: scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Scope the capturekitchen-masterentry
card intake notes read, capture rules locked
Show working prompt
Define the capture before transcribing a word. Step 1: read the card intake notes waiting in inbox/ and the recipe book's store (recipes.json) — what is already in the book and how entries are shaped. Step 2: lock the capture rules — the original wording is preserved exactly, spelling quirks, margin notes and all; every recipe carries its provenance (whose card, whose kitchen, what they always changed); the standardized ingredients-and-steps block sits alongside the original text, clearly separated, never replacing it; anything unreadable becomes a question, not a guess. Step 3: write an acceptance-criteria checklist ('every card captured as its own recipe file under recipes/', 'original text verbatim with margin notes kept and marked', 'provenance line on every recipe', 'standardized block separate from the original', 'each captured recipe recorded in the book's store'). Call write_task_note with the card count + rules + checklist and write notes/scope.md. - Capture the cardsarchivist
one faithful recipe file per card, recorded in the book
Show working prompt
Capture each card against the locked rules. Step 1: for every card note in inbox/, write a recipe file under recipes/ — a title, the provenance line, the original text transcribed faithfully (margin notes included and marked as margin notes), and then a clearly separated standardized block with an Ingredients list and numbered steps. Step 2: record each captured recipe in the book's store through the project's recipe capabilities — title, provenance, and the file it lives in. Step 3: where the card is ambiguous or unreadable, keep the original as written and add the question inline rather than smoothing it over. Step 4: write a per-card capture log to notes/capture.md — what was captured, what was preserved as-is, what needs asking. Call write_task_note with the captured count.
- Write the capture logcopywriter
what went in, what needs a test-cook, questions for the family
Show working prompt
Write the capture log for the family from your notes. Step 1: list what went into the book this session — each recipe with whose card it was. Step 2: name what needs a test-cook before it counts as verified, and why (an ambiguous quantity, a step that assumes the cook's hands already knew). Step 3: list the questions for the family — margin notes worth explaining, names and dates worth pinning down — so the next phone call captures them. Step 4: keep it warm; this is family history in food form. Write report.md and call write_task_note with the captured count 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, notes/capture.md, and the recipe files under recipes/ and verify every criterion from notes/scope.md: every inbox card became its own recipe file, the original wording is verbatim (spot-check phrases against the card notes — no silent corrections), margin notes survived and are marked as such, every recipe carries a provenance line, the standardized block is present and separate from the original, and each captured recipe is recorded in the book's store. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to capture. 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: "capture" })` 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.
- capture a recipe card
- get this recipe into the book
- transcribe oma's card
- add a family recipe
- preserve this recipe
Source
View this craftbook on GitHub · MIT license