daily-planlisted

# Daily Plan Build the day plan for a FeatureBoard project (model + effort per ticket), apply it, then dispatch sub-agents on every planned ticket at the right model/effort tier. ## 1. Build and confirm the plan - Call `daily_plan` with `apply: false` (pass `budgetTokens` if the user gave a budget) and show the plan: ticket, model, effort, estimate, and the dispatch groups. - Pause for a go-ahead if anything looks off; otherwise continue. - Call `daily_plan` again with `apply: true` to stamp `model:`/`effort:` labels onto the tickets. ## 2. Dispatch - Research first (default ON): for `effort:high` or `research:on` tickets not opted out with `research:off`, call `prepare_research` and dispatch a haiku/sonnet research sub-agent (its `suggestedModel`) in parallel; the orchestrator saves each returned brief via `add_kb_doc` as `research/<ticket>` BEFORE the implementation dispatch, so those packets carry `researchBrief` + local `ragChunks` (BM25, zero-token) automatically. - For every ticket in `dispatch.parallel` (haiku/sonnet/opus): `set_status` In Progress, `get_work_packet`, and start a sub-agent at that model with the packet as its brief — these can run concurrently. Right after starting each one, call `record_dispatch` (`worker: "sub-agent"`, `model`, `parallel: true`) so `get_agent_monitor` and the board show it's running. - When parallel tickets touch DISJOINT code areas, give each its own isolated git worktree (`create_worktree`) so agents don't edit the shared repo