How to Give Claude Complex Multi-Step Tasks

Complex tasks fail when you ask Claude to do everything in one prompt. The opening is strong, the middle section loses focus, and the ending rushes through the hardest part. The fix is phase decomposition: break the task into stages, review each stage, and then proceed.

Why one-shot complex tasks fail

• Claude tries to address all requirements at once and each part gets shallow attention
• Errors in early steps compound into bigger errors in later steps
• You cannot redirect mid-task because Claude has already committed to an approach
• The output is too large to review effectively — you miss problems buried in the middle

Phase decomposition

Break any complex task into 3-5 phases. Each phase has one deliverable. You review the deliverable before the next phase starts.

Bad

Write a complete marketing strategy with messaging, competitive analysis, budget, and campaign calendar.

Better

Phase 1: Competitive analysis
Using the competitor notes I will paste, create a comparison table of positioning, pricing, and target audience for each competitor.
Wait for my review before proceeding.

Phase 2: Messaging framework
Based on the approved competitive analysis, draft messaging pillars that differentiate us.
Wait for my review.

Phase 3: Campaign calendar
Based on approved messaging, create a 90-day campaign calendar with channel, format, and key message for each item.

Best

We are building a marketing strategy for [PRODUCT] targeting [AUDIENCE].
I will provide source material at each phase.

Phase 1 — Competitive landscape
Input: I will paste notes from 3 competitor websites
Deliverable: Comparison table (positioning, pricing, target audience, key differentiator)
Rules: Only use claims from my notes. Mark gaps as "Not in notes."
STOP after this deliverable. I will review and approve.

Phase 2 — Messaging framework
Input: Approved competitive table + our product one-pager (I will paste it)
Deliverable: 3 messaging pillars, each with a headline, supporting points, and proof point
Rules: Each pillar must address a gap identified in Phase 1
STOP after this deliverable.

Phase 3 — Campaign calendar
Input: Approved messaging framework
Deliverable: 90-day calendar with: week, channel, format, key message, target pillar
Rules: Mix channels (email, social, blog). No more than 2 items per week.
Final output as a table.

The best version works because each phase has defined inputs, a single deliverable, specific rules, and a mandatory stop for review.

Defining handoffs between phases

A handoff is the output of one phase that becomes the input of the next. Make handoffs explicit so nothing gets lost between steps.

• Phase 1 output (comparison table) → Phase 2 input (competitive gaps to address)
• Phase 2 output (messaging pillars) → Phase 3 input (messages to distribute)
• Each handoff is a checkpoint where you can redirect before investing more time

Practical multi-step examples

• Content production: research → outline → section drafts → review → final edit
• Code feature: requirements → architecture decision → implementation → tests → review
• Business analysis: data extraction → trend identification → hypothesis → recommendation
• Hiring: job description draft → interview question set → evaluation rubric → scoring guide

Common multi-step mistakes

• Sending all phases in one message and not stopping for review between them
• Not defining what the deliverable looks like for each phase
• Skipping the review step to save time — errors compound into later phases
• Making phases too small (10+ phases) or too large (1-2 phases for a complex task)

Related reading: /blog/how-claude-agents-work for the agent concept overview, /blog/how-to-build-reliable-agent-workflows for error handling, and /blog/how-to-build-a-reusable-claude-workflow for turning multi-step processes into templates.