| name | task-breakdown |
| description | Decompose goals into actionable scheduled subtasks |
Task Breakdown
Break down a large goal into concrete, schedulable subtasks.
When to Use
- User describes a multi-step goal or project
- User says "help me plan", "break this down", or "how should I approach this"
- User wants accountability for a goal over days or weeks
Procedure
- Understand the goal — ask clarifying questions if the scope is unclear
- Decompose into subtasks — each should be:
- Specific and actionable (starts with a verb)
- Completable in one sitting (30 min to 2 hours)
- Independently meaningful — delivers visible progress
- Order by dependency — what must happen first? what can be parallel?
- Create a durable plan — use
createPlanRecord when the work should persist across sessions or needs verification
- Suggest a schedule — map subtasks to reasonable dates/times based on:
- User's timezone and typical availability
- Logical ordering and dependencies
- Buffer time between related tasks
- Offer to schedule — ask if the user wants reminders created for each subtask
- If confirmed, use createReminder or createRecurringTask for each one
- Track completion — update durable plan steps as the work progresses and use
verifyOutcome before marking important work done
Guidelines
- Keep subtask count reasonable — 3-8 for most goals, up to 12 for large projects
- Front-load the hardest or most uncertain tasks
- Include a "review progress" check-in task at the midpoint for longer plans
- Don't over-schedule — leave breathing room
- Adapt granularity to the user's experience level with the topic
- When the task is high impact or likely to span multiple sessions, prefer a durable plan over a one-off checklist in chat
