task-decomposer

Task Decomposer

Breaks natural-language problems into sub-tasks suitable for DAG nodes. The first step of the meta-DAG: before you can build or execute a DAG, you need to understand what the pieces are.

---

When to Use

✅ Use for:

• Breaking a vague problem into concrete sub-tasks
• Identifying phases, dependencies, and parallelization opportunities
• Determining which sub-tasks are concrete vs. vague (pluripotent)
• Selecting the appropriate domain meta-skill for decomposition

❌ NOT for:

• Building the DAG structure from sub-tasks (use dag-planner)
• Executing the tasks (use dag-runtime)
• Assigning skills to tasks (use dag-skills-matcher)

---

Decomposition Process

flowchart TD
  P[Problem description] --> M{Domain meta-skill available?}
  M -->|Yes| L[Load meta-skill phase pattern]
  M -->|No| R{Research needed?}
  R -->|Yes| RA[Research standard decomposition]
  R -->|No| Z[Zero-shot decomposition]
  
  L --> D[Apply phase pattern to problem]
  RA --> D
  Z --> D
  
  D --> C[Identify concrete sub-tasks]
  D --> V[Identify vague/pluripotent sub-tasks]
  D --> DEP[Map dependencies between sub-tasks]
  D --> PAR[Identify parallelization opportunities]
  
  C --> O[Ordered sub-task list with metadata]
  V --> O
  DEP --> O
  PAR --> O

Step 1: Domain Detection

Classify the problem into a domain to select the right meta-skill:

Domain Signals	Meta-Skill
"build", "implement", "code", "app", "website"	software-project-decomposition
"research", "analyze", "report", "synthesize"	research-synthesis-decomposition
"design", "UI", "wireframe", "prototype"	product-design-decomposition
"strategy", "market", "business", "revenue"	business-strategy-decomposition
"data", "model", "train", "predict"	ml-project-decomposition

If no meta-skill matches, fall back to zero-shot decomposition.

Step 2: Phase Identification

Apply the meta-skill's phase pattern. Not all phases apply to every problem.