daily_planlisted

# Daily Plan — plan → apply → dispatch → close out Turn today's slice of a FeatureBoard queue into an executed day of work, with each ticket routed to the cheapest Claude model that will do it well. ## 0. Preconditions - FeatureBoard MCP connected. Ask which board if ambiguous; check `get_scratchpad` for a staged `[DISPATCH ...]` block first — if present, that IS the plan: skip to step 3. - Verify git targets for the project (config/customPrompt) before any work: where do CODE commits go vs PROJECTPAD commits? They can differ. ## 1. Plan Call `daily_plan { project, budgetTokens?, sprint? }` (read-only preview). Show the user: ticket · model · effort · estimate, totals by model, cutline. Proceed unless something looks off (or the user asked to review first). ## 2. Apply Call `daily_plan { project, apply: true }` — stamps `model:` and `effort:` labels onto the planned tickets so the plan survives the session. ## 3. Dispatch **Model roster** (what each tier is trusted with): - **fable** — orchestration (that's you), cross-cutting design, spec/architecture review - **opus** — architecture, multi-file server changes, storage invariants, migrations - **sonnet** — standard implementation: UI, features, most bugs, integrations, tests - **haiku** — mechanical: docs/copy edits, label churn, data reshaping, renames For each ticket: `set_status` In Progress → `get_work_packet` → start a sub-agent (Agent tool) with the packet as its brief and `model` set from the ticket's la