synaptiai/agent-capability-standard/decompose
Claude Code and agent skill by synaptiai/agent-capability-standard
- community
Checking that the SKILL.md file is still in the repository.
Break a goal into subgoals, constraints, and acceptance criteria. Use when planning complex work, creating work breakdown structures, or defining requirements.
Install
npx vskill@latest install synaptiai/agent-capability-standard/decomposeSKILL.md
Intent
Break down a complex goal into smaller, manageable subproblems with clear boundaries, dependencies, and acceptance criteria. Enable parallel work and incremental progress.
Success criteria:
- Goal fully decomposed (no gaps)
- Subproblems are independently verifiable
- Dependencies are explicit
- Acceptance criteria are testable
- Decomposition depth is appropriate
Compatible schemas:
schemas/output_schema.yaml
Inputs
| Parameter | Required | Type | Description | |
|---|---|---|---|---|
problem | Yes | string | Problem to decompose | |
max_depth | No | integer | Maximum decomposition depth | |
strategy | No | string | Decomposition strategy |
Inputs not listed here are outside the capability's contract: a workflow step that binds them gets W604 (STANDARD v1.1 §5.5).
Procedure
1) Understand the goal: Clarify what needs to be achieved
- Parse the problem statement
- Identify success criteria
- Note implicit requirements
- Determine scope boundaries
2) Identify major components: Find natural divisions
- Functional areas
- Phases or stages
- User journeys
- Technical layers
3) Create subproblems: Define each component
- Clear, specific objective
- Bounded scope
- Measurable outcome
- Independent when possible
4) Define dependencies: Map relationships
- Which subproblems block others?
- Which can proceed in parallel?
- Are there shared resources?
- Create dependency graph (
dependencies, one edge per blocking pair)
5) Add acceptance criteria: Specify done conditions
- Testable conditions
- Measurable outcomes
- Quality requirements
- Edge case handling
6) Validate completeness: Check coverage
- Do subproblems cover entire goal?
- Any gaps or overlaps?
- Are boundaries clear?
- Is granularity consistent?
7) Recurse if needed: Decompose large subproblems
- Check against target granularity
- Decompose subproblems that are too large
- Maintain consistent depth
- Stop when atomic enough
Output Contract
Return a structured object:
Field Definitions
| Field | Type | Description | |
|---|---|---|---|
decomposition | object | Summary of decomposition | |
subproblems | array<object> | Flat list of all subproblems | |
structure | object | Problem hierarchy: the goal and its tree of subproblems | |
dependencies | array<object> | Subproblem dependency edges (from must finish before to) | |
constraints | array | Boundaries affecting subproblems | |
gaps | array | Missing coverage identified | |
overlaps | array | Redundant coverage identified | |
confidence | number | 0.0-1.0 based on completeness | |
evidence_anchors | array | References to requirements or sources the decomposition rests on | |
assumptions | array | Assumptions that affect the decomposition |
Examples
Example 1: Feature Decomposition
Input:
The work is scoped to the web application only, on a 4-week timeline.
Output:
Evidence pattern: Each subproblem has testable acceptance criteria, dependencies mapped.
Verification
- [ ] All aspects of goal covered
- [ ] No gaps in coverage
- [ ] No significant overlaps
- [ ] Acceptance criteria testable
- [ ] Dependencies form valid DAG
Verification tools: Read (for requirement analysis)
Safety Constraints
mutation: falserequires_checkpoint: falserequires_approval: falserisk: low
Capability-specific rules:
- Always verify completeness
- Flag gaps explicitly
- Resolve overlaps
- Ensure acceptance criteria are testable
- Note assumptions that affect decomposition
Composition Patterns
Commonly follows:
retrieve- Gather requirementsinspect- Understand existing systemexplain- Clarify goal before decomposing
Commonly precedes:
plan- Plan decomposed subproblems (REQUIRED by plan)prioritize- Order subproblemsschedule- Time-order subproblemsdelegate- Assign subproblems
Anti-patterns:
- Never decompose without understanding goal
- Never leave gaps unidentified
- Never skip acceptance criteria
Workflow references:
- See
reference/composition_patterns.mdfor plan requiring decompose
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/decompose/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/synaptiai/agent-capability-standard/decompose)