Free to read · no account needed

16 min · claude

Break multi-step work into Claude-friendly chunks

Goal: Stop dumping a whole project into one prompt—chunk into plan → approve → execute step → check.

Best for: Reports, multi-email campaigns, study plans, small automations you still supervise.

“Cowork” here means working *with* the model across steps, not letting an agent roam unsupervised. Each chunk has a done check before the next. This pairs with human-in-the-loop checkpoints and blast-radius thinking for anything that sends or deletes.

Multi-step “cowork” modes need a written Done and pause points. Without them, the agent keeps going past your comfort.

Write the pause phrase you will paste when nervous: “Stop. Show plan and wait.” Keep it in your notes app.

Why beginners skip this

Skipping the hard part of “Break multi-step work into Claude-friendly chunks” feels fine until a live thread pays the bill. Hold: Plan, approve, one step, check—never the whole project in one gulp—prove it on a real artifact, or skip the badge Mid-week cost shows up as rework, not as a missing bookmark.

Step 1 — Plan first

Do this step with a real artifact open—not from memory.

Task: [big goal]
Return a numbered plan of ≤7 steps.
Mark which steps need my OK before continuing.
Do not execute yet. Flag missing inputs as [TODO].

Step 2 — Execute one step

Example

Filled prompt

Goal: 3-email onboarding sequence for product X.
5-step plan ONLY. I approve before execute step 1. Ban one-gulp full copy.

What good output looks like

  • Pulls from Project/file named in the ask for “Stop dumping a whole project into one prompt—chunk”
  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-cowork-multi-step-tasks Done?

Step 3 — Check, then unlock next

After each chunk: run a 60-second eval (claims, fluff, next step). Freeze facts. High blast-radius steps stay human-gated.

Step 2 done. Critique against: clarity, invented facts, missing [TODO]s. Scores + fix list only. Do not start step 3.

One Artifact or one thread

Keep the plan and outputs in one place. Six parallel chats for one project recreate the mess you tried to escape.

Restate the approved plan steps 1–N and which are done. Then wait.
Example

Filled prompt

Goal: ship onboarding email sequence (3 emails) for product X.
Return a 5-step plan ONLY (no copy yet). I will approve before step 1 execute.
Each step needs Done + check. Ban one-gulp full draft.

What good output looks like

  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good”
  • One-minute check: does output match claude-cowork-multi-step-tasks Done?
  • Pulls from Project/file named in the ask for “Stop dumping a whole project into one prompt—chunk”

Save this card

Card: Plan, approve, one step, check—never the whole project in one gulp—prove it on a real artifact, or skip the badge. Keep this beside the tool; read before you start.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Open the Claude Project you will keep. Confirm standing instructions + the knowledge file for “Stop dumping a whole project into one” are current. Guide: claude-cowork-multi-step-tasks. If you only have a blank practice box, stop and fetch the real job first.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week in Claude: break one real multi-step job into plan → approve → one step → check. Refuse a single mega-prompt. Keep the step card on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed claude-cowork-multi-step-tasks, put 25 minutes on the calendar and redo once.

Pause phrase ready

Keep “Stop. Show plan and wait.” in notes. Paste it when nervous.

Ship the practice

Close the tab only after Practice now is done on a real artifact.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

After Practice now, write one line: what you will refuse next time. That line is the habit.

Check the unknown path

What should the model do when a field is missing—null, TBD, or ask you? Write it once in Boundaries.

Example

Filled prompt

Project: translate + localize 3 help articles EN→ZH-HK.
Plan 5 steps with approve gates. Execute step 1 only (glossary freeze).
Ban one-gulp all three.

What good output looks like

  • Pulls from Project/file named in the ask for “Stop dumping a whole project into one prompt—chunk”
  • One-minute check: does output match claude-cowork-multi-step-tasks Done?
  • Standing instructions respected; no silent scope creep
  • Decisions quoted or labeled Unclear — never “sounds good” [claude-cowork-multi-step-tasks#3]
Example

Filled prompt

Localize 2 help articles.
Plan 5 steps with gates. Execute glossary freeze only today.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

What good output looks like

  • Decisions quoted or labeled Unclear — never “sounds good”
  • Pulls from Project/file named in the ask for “Stop dumping a whole project into one prompt—chunk”
  • One-minute check: does output match claude-cowork-multi-step-tasks Done?
  • Standing instructions respected; no silent scope creep

Red flag

Starting chunk two before chunk one is accepted; goal drift between chunks; current chunk undefinable—stop.

Pitfalls

PitfallFix
One prompt for the whole projectPlan → chunks
Skipping OK gatesExplicit approve lines
Letting steps invent data ahead[TODO] rule
Parallel chats for the same planOne thread or Artifact

Practice now

Live card: one Claude artifact/diff/email pass for “Break multi-step work into Claude-friendly chunks” with Blind before share (Asia/Shanghai).

Today: split one multi-step job into 3–5 chunks with an acceptance line each. Finish and accept chunk one before starting chunk two (Asia/Shanghai).

Today card (copy) — claude-cowork-multi-step-tasks: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Plan, approve, one step, check—never the whole project in one gulp—prove it on a real artifact, or skip the badge

  • You can point to a dated refuse-line
  • You have one artifact path from tonight
  • You can teach the red flag in one sentence

Next

HITL checkpoints · Chaining · Blast radius · Claude Projects knowledge

Pair with today: open the first Next link (agents-human-in-the-loop-checkpoints) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start