--- name: journal-plans description: Load it when the user asks for a plan, phases or a roadmap, or a plan is started, advanced or finished. A plan moves on as its to-dos close: a phase completes, a checkpoint waits for you, and the last phase ends the plan. keywords: plans, plan commands: plans --- # Plans A plan moves on as its to-dos close: a phase completes, a checkpoint waits for you, and the last phase ends the plan. A plan is built in order. journal plan create "" --set goal="" --set depth=normal|thorough starts it building, at its phases stage. When the user asks for a plan in the chat, settle how thorough it must be first: take it from what they said, judge it yourself when the work makes it plain, and ask with a question when you cannot tell. A thorough plan is researched and has a to-do for every small thing. Add every phase with journal plan phase "" --when "<complete when>" (--checkpoint where the user should look before it goes on). Then journal plan stage <n> todos, file the rows and put each under its phase with journal plan todos <n> <phase> <rows...>, or board tickets with journal plan tickets <n> <phase> <tickets...>. When every phase has rows, journal plan ready <n> hands it to the user. A plan whose phases hold tickets gets a worker agent of its own when it first starts, in its own environment and worktree, and the journal starts each phase's tickets once the phase before is done. The environment's own agent stays a co-assistant: asked how a plan is going, it answers from journal plan progress <n>, which gives the phase it is in, the state of that phase's rows and tickets, and what happened last. When the user asks for a review of a plan, run journal plan review <n> before you dispatch the reviewers, then link their report with journal report link <report n> plan:<n>: a plan still under review goes back to building for you to revise and mark ready again. A plan under review cannot be approved: its Approve button is gone and the server refuses an approval until the review's report is linked and you mark it ready again. Only the user approves a plan, and then you start it with journal plan start <n>; only the user continues it past a checkpoint; with the auto feature on, checkpoints are passed without waiting. You work one plan at a time. Starting a plan parks the one that runs, unless it is delegated: a plan is flagged delegated by itself when you hand a helper a row of its current phase (journal helper dispatch --todos) or when its worker agent starts, and a delegated plan keeps running beside the one you start. journal plan delegate <n> flags a plan by hand, and --off clears the flag once the helpers are done. The viewer shows a bar for each active plan and tags a delegated one with its helpers. journal plan park <n> sets a plan aside; a parked plan's rows wait until it is started again. Its lines and guards are for the main agent only; none reach a subagent.