Review a week and re-plan
review_weekUse this when the user comes back after a lane plan and says what got done, for example "here is my list with what I ticked, plan next week". Pass checklist: the todo_text from plan_lanes with [x] on finished lines (it carries the lanes and hours). Or, when the user tells it in words, pass lanes (build, reading, open and parking_lot names as the user gives them) with done and not_done task titles in the user's words, plus hours_per_week. Optional: start_date, days, days_off, next_steps for the build lane, swap_in to move a parked interest into the open slot, keep_hours. Returns what got done per lane, the changes it made (carried build steps, a paused side quest when build stalled, fewer hours after a week under 40%), and the next plan in the same shape as plan_lanes, with new todo_text.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many days to plan, 3 to 7. Defaults to the length of the pasted plan, else 7. | |
| done | No | Finished tasks: their titles as written, or their ids such as d1-1. | |
| lanes | No | The lanes object plan_lanes or review_week returned. Needed only when no checklist is sent. | |
| spine | No | The user's own one-sentence direction that ties the interests together. Leave it out to get a first guess. | |
| swap_in | No | A parked interest the user wants in the open slot now; the current side quest is parked with a bookmark. | |
| days_off | No | Weekdays with no tasks, such as ["Sun"]. Defaults to the days off in the pasted plan. | |
| not_done | No | Unfinished tasks: titles or ids. | |
| checklist | No | The plan text from todo_text with each finished line ticked as [x], sent whole from its first line "Lane plan: ...". Its 4 header lines carry the lanes, the hours and the parking lot, so nothing else is required. | |
| keep_hours | No | Keep hours_per_week even when less than 40% got done. By default the next plan uses 20% fewer hours then. | |
| next_steps | No | New next steps for the build lane, after the carried ones. | |
| start_date | No | First day of the plan as YYYY-MM-DD. Use today in the user's time zone, even mid-week: do not move it to a Monday or to tomorrow unless the user asked to start then. Defaults to today (UTC). | |
| hours_per_week | No | Hours for the next plan. Defaults to the hours in the pasted text. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | Yes | ||
| lanes | Yes | ||
| notes | Yes | ||
| spine | Yes | ||
| budget | Yes | ||
| review | Yes | ||
| status | Yes | ||
| changes | Yes | ||
| next_step | Yes | ||
| todo_text | Yes |