decompose
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Break a task into ordered subtasks with dependencies
28 other projects use a version of this.
Adopted by
Most recently taken up by
- aunysillyme-dev/aunx-decomposetheir own version, first seen Nov 15, 2026
- chippingway/chipping-orchestratortheir own version, first seen Nov 11, 2026
- TserenTserenov/FMT-exocortex-templatetheir own version, first seen Nov 2, 2026
- iwesys/IWEtheir own version, first seen Nov 1, 2026
- synaptiai/agent-capability-standardtheir own version, first seen Nov 1, 2026
- stoa-platform/stoatheir own version, first seen Nov 1, 2026
Used with
Projects with it also use idea, discover and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
szweibelSkillidea
Generate a wide field of options when the user is brainstorming, exploring, expanding, or pressure-testing — not recommending or implementing
Also in 3 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 3 projects that use this
MicrosoftSkilldiagnose
Use to systematically diagnose why scenarios fail — identifies root causes by analyzing agent traces, codebase, and behavioral patterns
Also in 4 projects that use this
GitHubSkillprd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Also in 3 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 6 projects that use this
MicrosoftSkillinit
Also in 3 projects that use this
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- anyproto/anytype-swift★ 525same name
- TserenTserenov/FMT-exocortex-template★ 64same name
- drafthq/draft★ 40same name
- chippingway/chipping-orchestrator★ 18same name
- matt-k-wong/mkw-DAG-architect★ 15same name
- vulca-org/vulca-visual-control-sdk★ 15same name
- stoa-platform/stoa★ 9same name
- flpbalada/fb-skills★ 8same name
- tercel/spec-forge★ 8same name
- synaptiai/agent-capability-standard★ 7same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- auditSkill
- dev-allSkill
- dev-investigateSkill
- devSkill
- digSkill
- investigateSkill
- prSkill
- reviewSkill
- tech-debtSkill
- update-docsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 12 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
After investigation and dig phases are complete
- Distinctive: line 16
When the approach is confirmed and decisions are made
- Distinctive: line 17
Before starting the implementation loop
- Distinctive: line 30
If a task feels larger, split it further
- Distinctive: line 42
Read CLAUDE.md to understand the project's architecture layers, then split by layer from inner to outer.
- Distinctive: line 77
Implementation + test = 1 task: Never separate implementation from its test
- Distinctive: line 78
Cross-cutting checks = last task: After all implementations are done
- Distinctive: line 84
All tasks block cross-cutting checks
- Very specific: line 88
Use TaskCreate for each subtask:
- Distinctive: line 103
After creating all tasks, show the full task list with dependencies:
- Distinctive: line 116
Ask user to confirm before starting implementation.
- Distinctive: line 122
After generating the full task list, use Codex to validate the decomposition.
- Distinctive: line 153
If Codex suggests corrections:
- Very specific: line 159
If ToolSearch fails to find Codex or the call errors:
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Task Decomposition
Break down a development task into small, executable subtasks with clear dependencies.
When to Use
- After investigation and dig phases are complete
- When the approach is confirmed and decisions are made
- Before starting the implementation loop
Input Requirements
You need these before decomposing:
- Investigation results (affected files, data flow, impact)
- Decision matrix from dig phase (resolved ambiguities)
- Confirmed approach
Decomposition Rules
Size
- Each task should take 5-30 minutes to implement
- If a task feels larger, split it further
Structure per Task
Each task must include:
- What: What to implement/change
- Where: Target file(s) with paths
- How: Specific implementation approach
- Why: Reason this change is needed
- Verify: How to confirm it works (test command, manual check, etc.)
Architecture-Based Ordering
Read CLAUDE.md to understand the project's architecture layers, then split by layer from inner to outer.
General pattern (adapt to project):
1. Core types — data classes, interfaces, enums
2. Business logic — use cases, services, domain rules
3. Infrastructure — repositories, API clients, DB
4. Presentation — UI components, view models, controllers
5. Tests — unit tests, integration tests
6. Cross-cutting — lint, formatting, CI checksFor KMP projects:
1. commonMain API — shared types, interfaces
2. expect/actual — platform abstractions
3. androidMain — Android-specific implementation
4. iosMain — iOS-specific implementation
5. Tests — commonTest, platform tests
6. Sample apps — androidApp, iosApp
7. Cross-cutting — detekt, explicitApiFor web projects:
1. Types/schemas — shared types, API contracts
2. Backend logic — API handlers, services
3. Frontend logic — state management, hooks
4. UI components — views, pages
5. Tests — unit, E2E
6. Cross-cutting — lint, buildPairing Rules
- Type + mapper = 1 task: Data type and its transformation go together
- Implementation + test = 1 task: Never separate implementation from its test
- Cross-cutting checks = last task: After all implementations are done
Dependency Order
Set dependencies on tasks that require earlier ones:
- Core type tasks block implementation tasks
- Implementation tasks block test tasks
- All tasks block cross-cutting checks
TaskCreate Format
Use TaskCreate for each subtask:
subject: "Implement {What} in {Where}"
description: |
**What**: {description}
**Where**: {file path(s)}
**How**: {implementation approach}
**Why**: {reason}
**Verify**: {verification step}
activeForm: "Implementing {What}"Output
After creating all tasks, show the full task list with dependencies:
| # | Layer | Description | Blocked By |
|---|-------|-------------|------------|
| 1 | Core | Define FooData data class | — |
| 2 | Logic | Implement FooService | #1 |
| 3 | Infra | Add FooRepository | #2 |
| 4 | UI | Add FooScreen component | #2, #3 |
| 5 | Test | Unit tests for FooService | #2 |
| 6 | Cross | Lint + format check | #3, #4 |Ask user to confirm before starting implementation.
Codex Architecture Validation (Optional)
After generating the full task list, use Codex to validate the decomposition.
Load Codex
ToolSearch("select:mcp__codex__codex")Call Codex (if available)
mcp__codex__codex(
prompt: "Validate this task decomposition for correctness and completeness:
## Task List
{full task table with dependencies}
## Project Architecture
{architecture layers from CLAUDE.md}
## Validation Checklist
1. **Layer ordering**: Are tasks ordered inner-to-outer (core → logic → infra → presentation → tests → cross-cutting)?
2. **Missing tasks**: Are there any steps that should exist between tasks? Any gaps?
3. **Dependency correctness**: Are all dependency edges correct? Any missing or unnecessary dependencies?
4. **Parallelization**: Which tasks could safely run in parallel (no shared state, no dependency)?
5. **Risk assessment**: Which tasks are highest-risk and might need extra verification?
Output: validated task list with any corrections, plus a list of parallelizable task groups."
)If Codex suggests corrections:
- Apply the corrections to the task list
- Note what was changed and why
Fallback (Codex unavailable)
If ToolSearch fails to find Codex or the call errors:
- Skip validation — output the task list as-is (traditional flow)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

