Pre-Departure Countdown
Audit a trip's readiness in the final stretch before departure: verify documents and bookings, close the packing gaps against the packing roster, sweep home-prep tasks, and produce a day-by-day countdown checklist to the departure date — so the last week runs on a list, not on 3am worry. Locks the audit areas and the days remaining FIRST, then audits each area against the trip record, then writes the countdown. Use for pre-trip checks, departure prep, 'are we ready for the trip', and travel countdown checklists.
Steps
Entry step: scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Scope the countdownplannerentry
days remaining, audit areas, readiness criteria
Show working prompt
Define the audit before checking anything. Step 1: read trip.json and packing.json from the workspace — the destination, the departure date and days remaining, the planned days, and the packing roster's packed/unpacked split. Step 2: fix the audit areas — documents (passports/IDs valid, visas if needed), bookings (transport, lodging, the first day's plan), packing (the roster, plus anything the itinerary implies that isn't on it), money and phones (cards that work there, plans that roam), and home prep (mail, plants, locks, who has a key). Step 3: agree the readiness criterion per area — what 'checked' concretely means. Step 4: write an acceptance-criteria checklist ('every area audited with its criterion', 'every itinerary-implied item is on the packing roster', 'every open item lands on a specific countdown day', 'the checklist ends at walk-out-the-door'). Call write_task_note with days-remaining + areas + checklist and write notes/scope.md. - Audit readinessreviewer
check each area, grow the packing roster, list open items
Show working prompt
Audit each area against its criterion. Step 1: walk documents, bookings, money/phones, and home prep with the owner — record each as ready or open-with-what's-missing. Step 2: read the itinerary's planned days and derive what they imply for packing (boots for the walking day, adapters, medications for the length of the trip); add anything missing to the packing roster through the project's trip capabilities. Step 3: list the packing roster's remaining unpacked items. Step 4: for every open item, capture the concrete closing action and how long it takes (some need a week — expedited documents; some need an hour). Step 5: write the audit results to notes/audit.md and call write_task_note with ready/open counts per area.
- Write the countdowncopywriter
day-by-day checklist to departure
Show working prompt
Write the day-by-day countdown from the audit. Step 1: place every open item and every unpacked-item batch onto a specific day between now and departure, longest-lead-time first, packing finishing the day before, not the morning of. Step 2: keep each day's load honest — a few items a day beats a heroic final evening. Step 3: write the departure-day section — the walk-out list (documents in hand, phone charged, home-prep final steps) in the order they happen. Step 4: top the page with the trip, the departure date, and the days remaining, so the list orients anyone who picks it up. Step 5: keep it one page. Write report.md and call write_task_note with the report path and the heaviest day.
- 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 and notes/audit.md and verify every criterion from notes/scope.md: every audit area appears as ready or open, every itinerary-implied packing item made it onto the roster (spot-check two planned days), every open item and unpacked batch sits on a specific countdown day with lead times respected (nothing week-long scheduled for the last day), and the departure-day walk-out list is present and ordered. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to countdown. 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: "countdown" })` 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.
- are we ready for the trip
- pre departure checklist
- trip countdown
- before we leave
- departure prep
Source
View this craftbook on GitHub · MIT license