Menu

Individual skill

task-decomposition

0upvotes

Breaking complex user goals into subtasks that agents can handle.

skills/design-agent-orchestration/task-decomposition/SKILL.md

Read pinned source

Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
203
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Task Decomposition
Users come with goals, not subtasks. Task decomposition is how a multi-agent system breaks a complex user goal into pieces that individual agents can handle — and then reassembles the results into something coherent.
## Decomposition Strategies
- **Sequential decomposition**: Break the goal into ordered steps. Step 1 must complete before Step 2 starts.
- **Parallel decomposition**: Break the goal into independent parts that can be worked on simultaneously.
- **Hierarchical decomposition**: Break the goal into sub-goals, then break each sub-goal into tasks.
- **Conditional decomposition**: The next step depends on the result of the current step. Different results lead to different paths.
- **Iterative decomposition**: Start with a rough version, then refine through multiple passes.
## Designing Decomposition Rules
For each type of user goal the system handles:
- **What's the entry point?** How does the system receive the goal?
- **What are the subtasks?** List all possible subtasks for this goal type.
- **What are the dependencies?** Which subtasks depend on others' outputs?
- **What's the critical path?** Which sequence of subtasks determines the minimum completion time?
- **What can be parallelised?** Which subtasks can run simultaneously?
Back to top