Break a Complex Task into Prompt Steps
The decomposition method for AI work: clarify the outcome, split into components with dependencies, sequence by risk, execute one component per prompt.
Overview
When a task feels too big to prompt, the instinct is to write a bigger prompt. The working move is the opposite: decompose. This resource teaches the method on a deliberately messy goal — planning a customer conference — that fits no specialty workflow. The generated sequence shows decomposition as a repeatable procedure: define what done looks like, break the goal into components with explicit dependencies, gather inputs before producing anything, and give every component its own focused prompt.
Workflow
-
Build with the loaded goal
The conference goal at 5 steps shows the core decomposition arc: define, split, sequence, execute, review.
-
Watch the risk ordering
Step 3 puts highest-risk components earliest — problems surface while there's still time to react.
-
Run your own goal
Any goal that feels too big: paste it, pick General, start with 5 steps.
Why This Works
- Decomposition converts one impossible prompt into several easy ones
- Dependency-aware components stop circular work — nothing runs before its inputs exist
- Risk-first sequencing front-loads the discoveries that would otherwise sink the plan late
Best for
- Cross-functional projects with many moving parts
- Goals where the components and dependencies aren't obvious upfront
- Anyone who keeps restarting big prompts from scratch
Not for
- Tasks that are actually simple — decomposition has overhead; respect it
- Cleaning up one overgrown prompt — that's the Prompt Cleaner
Use cases
- Decomposing a goal that doesn't fit any specialty workflow
- Converting 'this is too big to prompt' into an executable plan
- Practicing risk-first sequencing on a real project