IntermediateLesson 11 of 305 min read

Breaking big tasks into steps

Learn task decomposition: why small steps beat one giant prompt, how to plan stages, where to put checkpoints and when not to split.

In this lesson you will

  • Explain why decomposition improves results
  • Plan a job in stages
  • Pass inputs between steps
  • Place human checkpoints

About 16 minutes

The giant prompt that does everything badly

Zara has to write a fifteen-page report for her club’s annual meeting. She pastes her notes into an AI and types: Write the full report, make it engaging, check the facts, add a summary and suggest improvements. What comes back is smooth and thin. Some facts are wrong, the structure is generic and she cannot tell which parts to trust. In the Beginner lessons you learned to write one good prompt. This lesson teaches the next level: task decomposition, breaking a big job into small steps that you can check one at a time.

Why smaller steps work better

  • Focus. One clear goal per prompt means each part gets full attention.
  • Checkpoints. You can read and correct the result of step 1 before step 2 builds on it. Errors stop early.
  • Different methods. A fact-gathering step needs strictness; a drafting step needs fluency; a review step needs scepticism. One prompt cannot be all three.
  • Easier fixing. When the final result is poor you know which step to repair.
  • Reuse. A good step prompt can be used again in other jobs.

How to decompose a task

  1. Write the end product in one sentence: what exactly will exist when you are finished?
  2. Ask what a careful human would do, in order. Collect, outline, draft, check, polish is a common shape.
  3. Make each step produce something visible: a list, an outline, a draft section, a verdict.
  4. Decide where you must look: put a human check after steps where mistakes would spread.
  5. Write each prompt with its own role, task, context and format.

The usual stages

Stage Purpose Typical prompt
Collect Gather facts from your material List every fact in my notes; mark gaps as MISSING
Plan Choose structure and angle Propose an outline with 5 sections and the aim of each
Draft Write one piece at a time Write section 2 only, 150 words, using facts 3 to 7
Check Find errors and gaps List any claim that is not supported by the facts list
Polish Tone, flow and length Tighten to 120 words, keep every fact, plain tone

A decomposed plan in code

A plan is just an ordered list of prompts. This tiny program prints a four-step plan and counts the words, to show that four short prompts are easy to read and manage. It was run for real:

plan = [
    ("Collect", "List every fact about the event from my notes. Mark gaps as MISSING."),
    ("Structure", "Turn the facts into an outline with 5 sections."),
    ("Draft", "Write section 1 only, 120 words, from the outline."),
    ("Review", "Check the draft against the facts list. Report any claim not in the list."),
]
for number, (name, instruction) in enumerate(plan, 1):
    print(f"Step {number} - {name}: {instruction}")
print()
print("Steps:", len(plan), "| Words in all prompts:", sum(len(i.split()) for _, i in plan))
Step 1 - Collect: List every fact about the event from my notes. Mark gaps as MISSING.
Step 2 - Structure: Turn the facts into an outline with 5 sections.
Step 3 - Draft: Write section 1 only, 120 words, from the outline.
Step 4 - Review: Check the draft against the facts list. Report any claim not in the list.

Steps: 4 | Words in all prompts: 45

Passing results forward

Each step needs the right input. Do not assume the AI remembers everything perfectly in a long chat. For key steps, paste what the step needs, clearly labelled:

STEP 3 - DRAFT
Using only the outline and facts below, write section 1 in 120 words. Friendly, plain tone.

OUTLINE:
[paste the approved outline]

FACTS:
[paste the confirmed facts list]
Good to know

In a short chat the earlier steps stay in view, which is convenient. In a long chat details drift. For important jobs, paste the approved facts and outline into each new step or even a fresh chat.

Good checkpoints

  • After collecting facts: is anything wrong or missing?
  • After the outline: is the order logical and is anything out of scope?
  • After each draft section: are all claims in the facts list?
  • Before sending or publishing: read it fully, aloud if you can.

When not to split

Tiny tasks (rewrite this sentence, give me three titles) do not need a plan. Splitting adds effort. Use decomposition when the job has several different kinds of work, when mistakes would be costly or when the first one-shot result disappointed you.

Practice

Choose a job you would normally ask for in one go: a study guide, a trip plan, a product launch message. Write the end product in one sentence and list four steps with their outputs. Then run steps one and two and look at how much more control you have than with a single prompt.

Practice answer

A study guide could be: (1) list the key topics from my notes, (2) rank them by exam weight and my confidence, (3) write a one-page summary for the top three, (4) make five practice questions from the summary. Notice that each step has an output you can read before moving on.

Common mistake

Splitting into too many steps and losing the thread. Three to six steps cover most jobs. If you need more, group them into stages.

Number your steps in the prompt

Start prompts with STEP 2 OF 5 and a name. It reminds you and the AI where you are, and makes your prompt library easier to reuse.

Check what you learned

Five quick questions. Pick an answer and you will see straight away whether it is right and why.

What is task decomposition?

  1. Shortening a prompt
  2. Breaking a big job into small checkable steps
  3. Deleting facts
  4. Using more adjectives

Small steps give focus and control.

A key benefit of steps is…

  1. The AI never errs
  2. No facts are needed
  3. Chats become shorter
  4. You can check each result before the next step

Errors stop early.

What should every step produce?

  1. Something visible you can check
  2. Nothing
  3. A long essay
  4. A secret

Visible outputs enable checkpoints.

Why paste inputs into key steps?

  1. To make prompts longer
  2. To confuse the AI
  3. Details can drift in long chats
  4. To save money

Pasting the approved material keeps it exact.

When is splitting unnecessary?

  1. For every task
  2. For big reports
  3. For costly mistakes
  4. For tiny tasks like rewriting one sentence

Use it when it earns its effort.

Summary

  • Break big jobs into steps that each produce something checkable.
  • Typical stages: collect, plan, draft, check, polish.
  • Paste approved inputs into key steps.
  • Skip splitting for tiny tasks.

Next lesson

Next: structured output, getting tables, lists and JSON you can use.

Questions

How many steps should a plan have?

Usually three to six. Group more into stages.

Can I do all steps in one chat?

Yes, but for important jobs paste the approved inputs again or start a fresh chat to avoid drift.

Is this slower?

Slightly, but you spend less time fixing errors and rewriting.

Progress is saved in this browser.