Plan the Week
Start Monday with the week already shaped: every meeting seen, the ones needing prep flagged, the conflicts and overload called out, and real focus blocks defended — a plan you made once, on purpose, instead of a calendar you react to all week. Locks the week's events and the planning rules FIRST, then shapes the days, then writes the plan with its prep queue. Use for weekly planning, monday morning planning, 'what does my week look like', calendar reviews, and defending focus time.
Steps
Entry step: scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Scope the weekplannerentry
the week's events, the flags, the planning rules locked
Show working prompt
Define the week before shaping a single day. Step 1: read the week's events — from calendar.json in the workspace when the calendar syncs to a file, or through the project's calendar capabilities when it is wired as a live service — and read followups.json for the open follow-ups carried into this week. Step 2: sweep the events for what needs attention: meetings with no agenda or unclear purpose (they need prep), pairs that overlap or butt against each other with no gap, and days so full that real work cannot happen. Step 3: lock the planning rules — every meeting that needs prep gets flagged with what to prepare, every conflict gets named with a proposed resolution, focus blocks get placed on the emptier days, and open follow-ups land on specific days. Step 4: write an acceptance-criteria checklist ('every event this week appears in the plan', 'each prep-needed meeting is flagged with what to prepare', 'every conflict named with a proposed fix', 'focus blocks placed in real gaps', 'the load picture is honest — no day pretends to have room it lacks'). Call write_task_note with the event count + flags + checklist and write notes/scope.md. No planning yet. - Shape the daysplanner
day-by-day plan, focus blocks placed, conflicts resolved on paper
Show working prompt
Shape the week day by day against the locked rules. Step 1: lay out Monday through Friday — each day's meetings in order, with the gaps visible. Step 2: place the focus blocks into the real gaps, the biggest work into the biggest gap, and mark them as commitments, not leftovers. Step 3: for each flagged meeting, note what the prep is and which earlier day the prep happens. Step 4: resolve the conflicts on paper — which meeting moves, shortens, or gets a delegate — as a concrete proposal the owner can act on with one decision each. Step 5: distribute the open follow-ups onto specific days that have room for them. Write the day-by-day plan to notes/plan.md and call write_task_note with the shape of the week in one line per day.
- Write the week plancopywriter
the Monday-morning page: days, prep queue, conflicts and calls
Show working prompt
Write the week plan the owner reads Monday morning. Step 1: open with the week in one honest paragraph — how heavy it is, where the crunch lands, where the room is. Step 2: the day-by-day plan — each weekday with its meetings, focus blocks, and follow-ups, readable at a glance. Step 3: the prep queue — every meeting needing prep, what to prepare, and the day the prep is scheduled. Step 4: the conflicts and calls — each overlap with its proposed fix, so resolving them is one decision each, not a puzzle. Step 5: keep it one page and warm; this is a plan made once, on purpose. Write report.md and call write_task_note with the focus-block count and the prep-queue length.
- 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/plan.md and verify every criterion from notes/scope.md: every event in the week's calendar appears in the plan (count them against the events you read), each prep-needed meeting carries a concrete prep note scheduled on an earlier day, every conflict is named with a proposed resolution, focus blocks sit in real gaps on the page, follow-ups have landed on specific days, and the load picture is honest. Write PASS/FAIL per criterion; on any failure, name the gap and loop back to report. 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: "report" })` 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.
- plan the week
- plan my week
- what does my week look like
- monday planning
- set up the week
Source
View this craftbook on GitHub · MIT license