Magic To-Do
Break one task the user must do personally into small, concrete steps. A spice level (1 to 5) sets how small the steps get.
When to use
Break a task down when the user has to do it personally and either:
- they ask for it or signal trouble starting ("todo", "stuck on", "can't start", "overwhelmed", "keep avoiding", "break this down", "spice N"), or
- nobody asked, but a reply or plan ends with work only the user can do that takes more than 15 minutes.
Skip it when:
- The agent can do the work ("fix the bug", "draft the email"). Do the work. Never hand the user a checklist for a job the agent can finish.
- The task is one action under 5 minutes. State the action.
- Nobody asked and the user's part is under 15 minutes. List the actions plainly, with no spice line and no push offer.
- The user is reviewing a whole backlog. Show the list, then break down only the top item.
- The user says "no breakdown" or "just tell me". Give the one first action, written so it works without facts you don't have, and skip the breakdown for the rest of that topic.
One task per breakdown. If the user gives several, break down the most urgent one (money and hard deadlines first) and list the rest by name.
Spice levels
Spice = how hard or stressful the task feels to the user, not how hard it is. Higher spice means smaller steps, so starting takes less willpower.
| Spice | Name | Max per step | Typical steps | Use for |
|---|---|---|---|---|
| 1 | Mild | 30 min | 3-4 | Routine work done often |
| 2 | Medium | 15 min | 5-7 | Normal tasks (default) |
| 3 | Hot | 10 min | 8-10 | Tasks that have been put off |
| 4 | Very hot | 5 min | 11-15 | Dreaded tasks: chasing money, tax or government forms, hard conversations |
| 5 | Fire | 2 min | 16-25 | Full paralysis. Include physical micro-steps ("open the laptop", "open the bank tab") |
Max per step is the rule. The step counts are what a typical task comes to, not a quota: a small task gets fewer steps, and a big task gets more sittings, never bigger steps.
Picking the level when the user doesn't give one:
- Start at 2.
- +1 if the task has sat open for 7+ days (check its date in the task file if there is one), or the user says stuck, avoiding, or overwhelmed.
- +1 if it involves chasing money, a government portal, or a difficult conversation.
- Cap at 5. Say which level you picked and why in a few words, so the user can reply "spicier" or "milder".
Commands:
- "spicier" / "milder": redo at +1 / -1.
- "break step N down": run the skill on that one step at spice +1, numbered N.1, N.2, ...
- "next sitting": break down the next sitting of a task that was split.
Writing the breakdown
1. Read the context
Before writing steps, spend at most 3 quick reads on what the agent can see:
- The user's task file if one exists (
TODO.md, a notes vault, an issue tracker): the task's line, its date, and linked files. - The project or client notes the task names.
- The agent's memory for missing names, amounts, or deadlines.
Name real paths, people, amounts, and deadlines in the steps.
The first reply is always the breakdown. A question up front hands the user a decision before they have started, so a missing fact never becomes a question:
- The steps are the same either way: write the step so it works without the fact ("Open the portal you file on").
- The fact changes the steps: take the most likely reading, say so on the spice line ("Assuming a passport renewal, not a first passport. Say if that's wrong."), and write the steps for it.
- A name, amount, or date is missing: getting it is a step ("Ask Sam for the API key"). Never invent one.
2. Write the steps
- Each step is one action: one verb, one object. Never "and then".
- Steps are concrete: name the app, file, screen, or button. "Open the bank app > Statements > October" beats "check finances".
- Step 1 opens one thing: the exact file, URL, or app. It takes 2 minutes or less and needs no decision. Logging in, finding a password, and choosing between options are later steps.
- The last step is a visible finish line ("Tick the item in your to-do list").
3. Tag who does each step
[You]: only the user can do it. This always includes sending messages to other people, paying, filing, publishing, and deleting.[Agent]: the agent can do it (drafting, research, checking a record).[Name]: a teammate.
An [Agent] step that needs nothing from the user gets done before the breakdown is shown. List it as [Agent, done] with the result or file path. An [Agent] step that depends on a [You] step stays in the list; do it when the user reaches it.
4. Add the times
- Minutes at the end of every open step:
[5 min]. Use a range only when it is truly unknown:[10-20 min]. Done steps get no time. - Total line: the sum of the open steps, then a realistic block = sum x 1.5, rounded up to the next 5, to cover time blindness and switching cost.
- If the sum goes over 90 min, split the task into sittings. Write out sitting 1 in full and name each later sitting in one line with its rough time.
5. Group into phases
More than 5 steps: group them into phases of at most 5 steps, each with a short bold name and its minutes. The numbering runs straight through from 1 to N and never restarts, so "break step 7 down" always means one step.
Count before sending: a phase with 6 steps gets split into two phases.
Output format
The first line is the spice line. Leave a blank line after each phase name so the list numbers render as written. Step 1 is bold.
Spice 4 (Very hot): open 12 days + chasing money. Say "spicier" or "milder".
**Get ready (5 min)**
1. **[You] Open the last email thread with Acme [2 min, do now]**
2. [Agent, done] Drafted the reminder from `invoices/acme-oct.pdf`: `drafts/acme-reminder.md`
3. [You] Read the draft [3 min]
**Make it yours (8 min)**
4. [You] Check the amount and due date against the invoice [2 min]
5. [You] Change one line so it sounds like you [3 min]
6. [You] Paste the draft into a reply on the thread [2 min]
7. [You] Check the To line shows Priya at Acme [1 min]
**Send and close (7 min)**
8. [You] Attach `invoices/acme-oct.pdf` [1 min]
9. [You] Press send [1 min]
10. [You] Put "Acme follow-up" in your calendar for Friday [3 min]
11. [You] Tick "Chase Acme" in `TODO.md` [2 min]
Steps add up to 20 min. Block 30 min.
Done looks like: reminder sent, follow-up in the calendar.
Add to Todoist as subtasks? (yes / no)
No intro, no recap. One question at the end. No em dashes.
Push to a task manager (only after a yes)
- End with: "Add to as subtasks? (yes / no)". Never create tasks without a yes.
- On yes, use whatever task-manager tool the agent has (ClickUp, Todoist, Linear, Asana, GitHub Issues, a markdown file):
- Parent task: name = the task, estimate = the realistic block, description = source + spice level.
- One subtask per step, each with its own minute estimate, assigned to the user for
[You]steps.
- If no default list or project is known, ask once, then remember the answer.
- Verify: read the parent task back and report the subtask count and link. Don't report success before that.
- No task-manager tool? Offer a markdown checklist or an
.icsfile instead.
Pitfalls
- Don't break down tasks the agent should just do. Fake homework is the most common failure.
- Don't pad a list to reach a typical step count.
- "Decide X" is too big for one step. Make it "Pick A or B: A = ..., B = ..." with the options written out.
- Blocked on someone else: the breakdown is one follow-up with a deadline, then park it. Don't plan work that can't start yet.
- Task lists go stale. Check the linked notes first, so you don't plan a step that's already done.
Pairs with
adhd-mode in this repo, which shapes every reply and hands tasks that land on the user to this skill.