Daily plan
daily_planSelect the day's slice of queued tickets within a token budget, assign each ticket a model and effort level, and optionally apply labels to generate parallel dispatch groups for execution.
Instructions
Plan TODAY: pick the day's slice of the priority queue (default budget 5M logged tokens ≈ one day of a 25M week), assign each ticket a model from the roster (fable=orchestration/design, opus=architecture/invariants, sonnet=standard implementation, haiku=mechanical docs/copy) and an effort level (low/medium/high). apply:true writes model:/effort: labels onto the tickets. Returns dispatch groups: haiku/sonnet/opus tickets safe to run as parallel sub-agents, fable inline in the orchestrator (see server/routing.js). Pair with the daily_plan prompt to execute.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project": "<project>"
},
"name": "daily_plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| apply | No | Write model:/effort: labels to the planned tickets. | |
| sprint | No | Limit to one sprint. | |
| project | Yes | ||
| budgetTokens | No | Today's logged-token budget (default 650k; ~weekly 25M effective ÷ 5 days ÷ ×8 orchestration multiplier). |