Menu
Use when a problem feels too big or vague to start - decomposes it into pieces you can actually work on
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
| name | breaking-down-a-problem |
| description | Use when a problem feels too big or vague to start - decomposes it into pieces you can actually work on |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | simple |
| time | 10-20 min |
| version | 1.0.0 |
| source | bundled |
Turns "this problem is too big" into a one-page problem statement plus a list of subproblems sized so you can start work on the smallest one today.
This is a workflow.
Re-write the problem as one sentence with three parts: observed (what is happening), desired (what should be happening), gap (the difference).
Example: "Onboarding takes new users 14 days to reach activation; we want under 3 days; current funnel drops 60% on day 2."
What are the axes along which the problem could be split? Common axes: by user segment, by time/lifecycle, by component, by cause type, by responsibility, by cost.
Pick 1-2 axes that look most productive.
Along the chosen axes, list 3-7 subproblems. Each subproblem should be:
Of the subproblems, which can you start today with the inputs you have? That's your first move. Anything else is queued.
Read the breakdown back: does solving the subproblems together solve the original? If not, the decomposition missed something. Loop back.
Return to Stage 2 if Stage 5 reveals the breakdown doesn't reconstitute the original problem.
making-a-decisionInput: "Our product launch is going badly and I don't know what to fix first."