CourseLevel 5Guide 22
22🧭 Level 5 — Workflows & Automation

Chaining Claude: From Research to Finished Output

20 min readAdvanced

What you will learn

  • How to connect separate Claude steps — research, drafting, critique, polish — into one chain
  • What context to carry forward between steps, and what to deliberately drop
  • Why a separate self-critique step catches things a single long prompt won't

Difficulty: Advanced · Estimated time: 20 min

What You'll Learn

  • How to connect separate Claude steps — research, drafting, critique, polish — into one chain
  • What context to carry forward between steps, and what to deliberately drop
  • Why a separate self-critique step catches things a single long prompt won't
  • Why This Matters

    A single prompt caps out on complex output. Ask for research, a draft, and a polished final version all at once, and Claude optimises for finishing, not for quality at each stage — it's writing and judging its own work in the same breath. Splitting the work into a chain of focused steps, each with one job, consistently produces better output than one prompt trying to do everything.

    The Concept

    A typical chain looks like: research → draft → self-critique → final polish. Each step is its own prompt (or conversation), and the output of one becomes the input of the next.

    The part people get wrong is context handoff — deciding what travels forward. Carry forward the decisions and material (the key facts found, the draft itself, the brief). Don't carry forward the process (the back-and-forth it took to get there) — that's noise for the next step and wastes context. A clean handoff is a short, deliberate summary or the artefact itself, not a full transcript.

    The critique step matters most and gets skipped most. Running it as a genuinely separate pass — ideally in a fresh conversation — means Claude is reviewing the draft cold, not defending work it just produced moments ago.

    Step-by-Step

  • Research step: gather raw material — facts, source quotes, examples. Output: a structured set of findings, not prose.
  • Draft step: turn the findings into a first version against a clear brief (format, audience, length).
  • Self-critique step: in a fresh context, feed in only the draft and the original brief. Ask Claude to check it against the brief and flag weak claims, structure issues, or tone problems — not to rewrite yet.
  • Final polish step: feed the draft plus the critique back in and produce the finished version.
  • Define the handoff format at each boundary before you start — what exactly step 2 hands to step 3.
  • Example

    Building a client-ready "industry trends" LinkedIn carousel:

  • Research: Claude pulls and summarises five recent, relevant data points and sources on the topic
  • Draft: Claude turns those into carousel slide copy against the client's format brief
  • Self-critique (fresh chat): given only the draft and brief, Claude checks: does each slide earn its place, is any claim unsupported, does the hook work
  • Polish: the critique and draft go back in together, producing the final slide copy
  • Four short, focused passes beat one prompt asked to "research and write a great carousel."

    Try This

    Take a piece of content you'd normally write in one prompt. Split it into the four-step chain above and compare the result to your usual single-prompt version.

    Copy This

    CHAIN: [name]
    
    STEP 1 — RESEARCH
    Input: [topic/brief]
    Output: [structured findings — bullet points, not prose]
    
    STEP 2 — DRAFT
    Input: [findings from Step 1] + [brief: format, audience, length]
    Output: [first draft]
    
    STEP 3 — SELF-CRITIQUE (run in a fresh conversation)
    Input: [draft only] + [original brief]
    Output: [list of specific issues — no rewrite yet]
    
    STEP 4 — POLISH
    Input: [draft] + [critique from Step 3]
    Output: [final version]

    Common Mistakes

  • Carrying the entire research conversation forward instead of a clean summary — this bloats context and buries the useful material
  • Running the critique in the same conversation as the draft, so it's reviewing work it's primed to defend
  • Treating critique and polish as one step — separating "what's wrong" from "fix it" produces sharper feedback
  • No defined stopping point, so the chain runs an extra "just to be sure" pass that adds time without adding quality
  • Level-Up Tip

    Keep the research step's output in a durable format (a doc, a table) even after you've moved past it. When you rerun this chain in three months, you can skip re-researching and go straight to drafting.

    Action Checklist

    ○Split one piece of work into research / draft / critique / polish
    ○Defined exactly what gets handed forward at each boundary
    ○Ran the critique step in a fresh context, not the drafting one
    ○Compared the chained result against a single-prompt attempt

    Next Guide

    23 — Making Claude Part of How Your Team Actually Works


    Premium Content

    Levels 2–6 require a mygyaan membership to access the full guides.

    ₹1,000/month — full mygyaan.ai access (all modules)

    ₹3,000 one-time — this course only

    Free, forever

    Sign up free for mygyaan.ai

    One book, one learning story, one quote, one video — delivered every day at 7 am. Unlimited books and turnaround stories, no payment, ever.

    Free forever. By signing up you agree to our Terms and Privacy Policy.

    No password. No spam. Unsubscribe any time.