Use when the user wants to break down, decompose, scope, or think through a task that ALREADY exists in TickTick — "break down this task", "decompose <task>", "scope the thing in Personal", "help me think through <existing task>", or names/points at a captured task to split. Context-aware (work → pipeline stages, personal → free-form or none). For NEW work or a Linear ticket not yet in TickTick, use butler:intake instead.
Use when the user names an explicit Linear ticket ID, or describes a NEW piece of work not yet in TickTick and wants it turned into tasks — "start ABC-123", "scope this new work", "how should I approach X", "turn this into a task tree". Builds a durable task tree in TickTick. For breaking down a task that ALREADY exists in TickTick, use butler:decompose.
Use when the user wants to plan, time-box, or commit a work day in TickTick — "plan my day", "plan today", "plan tomorrow", "what should I work on today", end-of-day planning for the next day, or reconciling open work and committing a day's blocks. Schedules around Google Calendar commitments. Works for today (planned in the morning) or tomorrow (planned in the evening).
Use when today has slipped and the user wants to recompute the rest of the day — "reschedule", "I'm behind", "move my blocks", "things slipped", "shift my plan", "recompute from now". Recomputes today's remaining blocks from the current time around the remaining commitments. Never silently drops a must.
Use when the user wants to set up, configure, or reconfigure butler — "set up butler", "configure butler", "butler setup", "change my butler config", "what projects is butler using", or the first run when no config exists yet. Interviews for the user-specific values and writes the global config at ${CLAUDE_PLUGIN_DATA}/config.yaml. Re-runnable to update individual fields.