Break down a big task
Breaks an overwhelming task into concrete steps that each take under an hour, orders them by dependency, flags unknowns and picks the one step to do today. Use when a big task feels impossible.
Big tasks stall for predictable reasons: "done" is fuzzy, the first step is unclear or too big, hidden decisions and unknowns block progress, and the whole thing feels like one undivided lump. A good breakdown fixes all four: it defines the finish line, turns the lump into small physical actions, surfaces the unknowns as their own steps, and makes starting today easy.
Only if [DEADLINE] is given: Deadline and available time:
- Define done in one or two sentences: the concrete thing that will exist or be true when the task is finished. If the task description is too vague to define done (for example "sort out my life admin"), ask up to three short questions and stop.
- Break the task into steps. Each step:
- starts with a physical verb ("Email", "Draft", "List", "Call", "Book"), not "work on" or "think about";
- takes under 60 minutes; split anything larger;
- has a rough time estimate in minutes;
- produces something visible (a list, a draft, a sent message, a decision).
- Turn every unknown, decision or dependency on another person into its own early step ("Ask Ana which template to use"), because waiting on others is slow and should start first.
- Order the steps by dependency, then by what unblocks the most. Group them into three to six phases if there are more than ten steps.
- If a deadline was given, add up the estimates, compare with the available time, and say plainly whether it fits. If it does not, propose what to cut, simplify or ask for.
- Pick one step to do today: the smallest step that creates momentum or unblocks others. Write a two-minute starter for it (the very first physical move).
- Use the user's words and details; do not invent requirements, people, tools or deadlines. Mark assumptions as such.
- Estimates are rough and labelled as such; add about 25 percent buffer to the total because people underestimate.
- Keep it to the steps needed for done. Nice-to-haves go under "If you have more time".
- No motivational filler. The breakdown itself is the help.
Done looks like
One or two sentences.
Steps
A numbered checklist grouped by phase if needed: - [ ] Step (estimate). Mark steps that wait on someone else with "(waiting)".
Unknowns
Bulleted questions or decisions, each linked to the step that resolves it.
Do today
The chosen step, why it comes first, and the two-minute starter.
If you have more time
Optional extras, one line each.
If a deadline was given, add a one-line capacity verdict after the steps: total estimate with buffer versus time available.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Productivity and personal life
- category
- Task management
- level
- Beginner
- made for
- Anyone, personal use, Student, People manager, Founder / business owner
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install break-down-big-task --target claude-codenpx skills add hermes-hq/hodios-dist --skill break-down-big-task -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-productivity@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Task managementBeat procrastination on a task
Diagnoses why a specific task is being avoided, then gives a concrete two-minute first step, a plan for the next 25 minutes and a way to keep going. Use when you keep putting something off.
beat-procrastinationPlan my week
Builds a realistic weekly plan with time blocks from your tasks, fixed commitments and energy patterns, with buffers, a capacity check and a list of what will not fit. Use at the start of a week.
plan-my-weekWrite a project plan
Writes a lightweight plan for a non-software project such as an event, move, renovation or campaign, with milestones, owners, dependencies, risks and a check-in rhythm, worked back from the deadline.
write-project-planProductivity coach
Coaches people to get things done with systems rather than willpower, keeps plans realistic about time and energy, and checks in on progress without guilt. Use for ongoing accountability.
productivity-coachAudit where your time goes
Analyses a week of time tracking or calendar data to show where the hours actually go against stated priorities, finds the leaks and proposes specific changes. Use when busy but not productive.
audit-time-useBuild a reusable checklist
Builds a reusable checklist for a recurring procedure such as travel prep, month-end or event setup, ordered by timing, with pause points, commonly missed steps and a way to keep it current.
build-reusable-checklist