Skip to content

johnfkoo951/cmdspace-plugins / plugins/dev-orchestrator/skills/decompose

decompose

Verified

Task decomposition skill. When triggered by '/decompose', '작업 분해', 'break down this task', or '서브태스크로 나눠줘', this skill takes a complex task and recursively decomposes it into atomic, testable subtasks with tier assignments and parallelization opportunities.

FileKindSize
SKILL.mdskill md2.2 KB
---
name: decompose
description: >
  Task decomposition skill. When triggered by '/decompose', '작업 분해', 'break down this task',
  or '서브태스크로 나눠줘', this skill takes a complex task and recursively decomposes it
  into atomic, testable subtasks with tier assignments and parallelization opportunities.
---

# Decompose — Task Decomposition

Breaks complex tasks into atomic, executable subtasks.

## Workflow

### Step 1: Understand the Task

Read the user's request and any related files. If the task is ambiguous, use `AskUserQuestion` to clarify:

```json
{
  "questions": [
    {
      "question": "What granularity do you need?",
      "header": "Granularity",
      "options": [
        {"label": "Coarse (Recommended)", "description": "5-10 high-level subtasks, each ~1 agent session"},
        {"label": "Fine", "description": "10-30 atomic tasks, each ~1 function or file change"},
        {"label": "Sprint-sized", "description": "Grouped into workable chunks with effort estimates"}
      ],
      "multiSelect": false
    }
  ]
}
```

### Step 2: Decompose

Dispatch **planner** (Opus) to decompose the task:

1. Identify the major components of the task
2. For each component, break into subtasks
3. For each subtask, determine:
   - Description (specific and actionable)
   - Agent type and tier
   - Dependencies (what must complete first)
   - Parallel group (what can run simultaneously)
   - Estimated complexity (1-10)

### Step 3: Output Decomposition

```markdown
## Task Decomposition: [Original Task]

### Dependency Graph
```mermaid
graph TD
    A[Task 1.1] --> C[Task 2.1]
    B[Task 1.2] --> C
    C --> D[Task 3.1]
    C --> E[Task 3.2]
```

### Parallel Groups

**Group 1** (can run simultaneously):
| # | Task | Agent | Tier | Complexity |
|---|------|-------|------|------------|
| 1.1 | [Task] | [agent] | [tier] | [1-10] |
| 1.2 | [Task] | [agent] | [tier] | [1-10] |

**Group 2** (depends on Group 1):
| # | Task | Agent | Tier | Complexity |
|---|------|-------|------|------------|
| 2.1 | [Task] | [agent] | [tier] | [1-10] |

### Total Estimates
- Subtasks: [N]
- Parallel groups: [N]
- Estimated total complexity: [Sum]
- Tier distribution: Opus [N] / Sonnet [N] / Haiku [N]
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall