Task Decomposition
Complex tasks often fail because they're too big. Decomposition breaks them into smaller, manageable subtasks that AI can handle reliably.
The Problem with Complex Prompts
Loading Prompt Playground...
Decomposition Strategies
Horizontal (Parallel Subtasks)
Main task: Write a business plan
Subtasks (can be done independently):
1. Write executive summary
2. Research market analysis
3. Analyze competitors
4. Describe the product
5. Plan marketing strategy
Vertical (Sequential Dependencies)
Main task: Develop a feature
Subtasks (must be sequential):
1. Define requirements
2. Design architecture (needs #1)
3. Write code (needs #2)
4. Create tests (needs #3)
5. Document feature (needs #3)
Exercise: Decompose a Complex Task
Loading Exercise...
Subtask Prompt Design
Each subtask should be:
- Focused - One clear objective
- Complete - Contains all needed context
- Independent - Minimal dependencies when possible
- Verifiable - Clear success criteria
Loading Prompt Playground...
Combining Results
After decomposition, you need integration:
Final Prompt:
"I've completed these analyses:
[Market summary]
[Competitive analysis]
[Product description]
Now synthesize into a cohesive executive summary that ties together these insights. Maximum 300 words."
Exercise: Design a Decomposition Flow
Loading Exercise...
When to Decompose
Decompose when:
- Task has multiple distinct parts
- Output would exceed quality limits
- Different parts need different expertise
- Results need to be consistent across sections
Don't decompose when:
- Task is simple and focused
- Parts are highly interdependent
- Overhead of combining outweighs benefits
Practice: Decomposition Planning
Loading Prompt Playground...
Decomposition turns impossible tasks into achievable workflows.
Discussion
Sign in to join the discussion.
0 comments

