Lesson 27 of 32
The Unbroken Chain
Prompt Chaining
Instead of asking for the whole job in one prompt, break it into a short sequence - research, outline, draft, polish, translate - where each step's output becomes the next step's input, and you inspect it before passing it on. It works because a small step is something you can actually judge, and a mistake caught in the research never becomes a mistake printed in three languages.
Give each link its own tags and the chain will hold together across a long conversation: <chain_plan> at the top so it knows the shape of the race, <this_link> for the job in hand, <baton> naming precisely which earlier output to build on, and the stop instruction last, where it is obeyed most reliably. Because Claude handles a great deal of material comfortably, the whole chain can live in one chat without the early links fading. Ask for each link's output in its own Artifact, titled, so that at the draft link you can say "use the outline in the artifact called Outline v2" rather than "the outline above" - a named baton beats a gestured one. The chain recipe itself belongs in a Project.
From the book Claude handles very long material well, so a whole research-to-draft chain can live in one chat; ask it to put each link's output in an Artifact so you can edit or download the outline and draft between steps. Save your chain recipe in a Project so each new run follows the same steps.
- Tag the link: <chain_plan>, <baton>, <this_link>, stop instruction last.
- Name the artifact you are handing on, never "the outline above".
- Ask what is weakest in a link, not whether it is good.
- One Artifact per link makes re-forging a single link easy.
- Keep the chain recipe in a Project so each run matches.
Instead of
Write a business plan for our SHG pickle business.
Claude version
<who_we_are> Twelve women in a self-help group near Warangal. Between us we have kitchen experience, no business experience, and a small pooled fund. We can sell within our own and neighbouring villages to begin with. </who_we_are> <chain_plan> Four links, in order: shortlist products, outline a one-page plan, write the plan, render it in Telugu. I approve each link before the next begins. </chain_plan> <this_link> Link 1 only. Five pickles we could make from produce grown around Warangal. For each: rough raw-material cost per kg in rupees, how long it keeps without refrigeration, and how hard it would be to sell locally with one line of reasoning. Put it in an Artifact titled "Product shortlist" as a table. </this_link> <honesty> Underneath the table, name the two figures you are least confident about and say what they depend on. I would rather know which numbers are soft than discover it after we have bought vegetables. </honesty> <stop> End after the shortlist. No outline, no plan, no Telugu. I will choose three products and then open link 2. </stop>
Then loop it
- We choose mango, gongura and lemon. Taking only those three rows from the artifact "Product shortlist" as your baton, produce an outline for the one-page plan - products, costs, division of work, where we sell, first-month target - in a new Artifact titled "Outline v1". Headings and a line each. Then tell me which part of the outline the drafting step will struggle with most. Stop there.
- Move "where we sell" to the top and leave everything else. Save that as "Outline v2". Then, using "Outline v2" as the baton, write the full one-page plan in simple English in an Artifact titled "Plan - English".
- Using the artifact "Plan - English" exactly as it stands, write a Telugu version in a new Artifact titled "Plan - Telugu". Simple spoken Telugu that a member can read aloud at the meeting; headings in the same order; rupee figures left as numerals. Do not improve the content while translating - if something reads badly in Telugu, translate it faithfully and tell me separately.
Why it worksEach link has one job and a checkpoint, and every handoff names exactly which output to build on, so mistakes are caught long before the final Telugu version.
Instead of
Write a YouTube video about Gulmarg in winter.
Claude version
<my_channel> Hindi-English travel videos for budget travellers. The next one is a 10-minute guide to a winter day trip from Srinagar up to Gulmarg. </my_channel> <chain_plan> Link 1 research. Link 2 scene outline. Link 3 script. Link 4 title and description. One at a time. </chain_plan> <this_link> Twelve facts and tips my viewers would want: getting there and back within a day, rough costs in rupees, what winter clothing actually matters at that altitude, how gondola booking works, and the mistakes first-timers make. One line each, in an Artifact titled "Gulmarg research". </this_link> <verification> Tag with [check] every line that depends on something seasonal or administrative - fares, timings, road closures, booking rules. You are working from what you have read, not from this week, and I am the one who can confirm it on the ground. Over-tag rather than under-tag; an untagged wrong fare ends up in the script. </verification> <stop> Research only. No outline, no script, no titles. </stop>
Then loop it
- Checked locally: 4 and 11 were wrong, I have struck them out. Using facts 1, 3, 5, 7 to 10 and 12 from "Gulmarg research" as your baton, build a scene-by-scene outline for ten minutes with timings, in an Artifact titled "Scene outline". Before the outline, say in two lines where a day trip this short is likely to feel rushed on camera.
- Outline approved as it stands. Using the artifact "Scene outline" as the baton, write the full script in casual Hinglish with B-roll notes in brackets, in an Artifact titled "Script v1".
- Based on "Script v1" only - not the research - give me 5 title options under 60 characters and a 150-word description with chapter timestamps matching the outline. Keep these in the chat rather than an artifact; I will paste them straight into the upload page.
Why it worksEvery handoff names its baton - which facts, which outline, which script - and the [check] marks create a checkpoint before anything reaches the camera.
Instead of
Make a dengue awareness leaflet in Marathi.
Claude version
<reference_material> [Paste in whatever you already hold, and put it here rather than at the end: last year's leaflet, the municipal advisory, the notice the housing society circulated. Claude reads long material placed first and follows the instruction placed last.] </reference_material> <situation> I am an NGO volunteer in Pune. This sheet gets printed and pushed under doors during the monsoon, so whatever is wrong in it stays wrong on a few hundred doors. </situation> <scope_limits> Breeding prevention, and nothing adjacent to it. No medicine names, no home remedies, no symptom lists, no treatment. Exactly one clinical sentence is permitted in the finished sheet - "see a doctor if fever continues" - and not a word beyond it. If the line you are about to write crosses that boundary, stop writing and tell me instead. </scope_limits> <task> This is the first of four - then draft, then review, then Marathi - and our health centre stands between this step and the next. Propose eight household actions against breeding, one line apiece, with the body that recommends it in brackets. Open with two lines on anything in the material above you would not repeat this year, and why. Close by naming the two proposals the health centre is most likely to argue with; those are what I will raise with them first. Stop at the eight. Nothing is drafted while they stand unapproved. </task>
Then loop it
- The health centre approved tips 1 to 6 and added "empty flower-pot trays every week". Using those 7 tips as the baton, write the English leaflet in an Artifact titled "Leaflet - English": a headline, 7 short points, and a closing line with a space for [helpline number].
- Before the final link, write me a baton summary of this chain - the aim, the audience, the 7 approved tips, the scope limits and the tone - compact enough to paste at the top of a fresh chat. Put it in a separate Artifact titled "Baton summary".
- (In a new chat.) [Paste the baton summary, then the English leaflet beneath it.] Using the leaflet text above, write a simple spoken Marathi version for colony residents, keeping the same headings and order and leaving [helpline number] as it is. Flag any tip whose meaning you had to change to sound natural in Marathi - our health centre will re-check those lines.
Why it worksThe checkpoint lets a professional verify the facts before they flow into every later link, and the baton summary carries the chain cleanly into a fresh chat.
Loop it
Treat every link as its own small loop. Read each output before you pass it on: are the facts right, is anything missing, is the order sensible? Fix it there - "Change point 3, then show me the corrected outline" - and only then hand off with a named baton: "Using the corrected outline above, now…". If a later link goes wrong, return to that link alone instead of restarting the chain. When the conversation grows long, ask for a baton summary and continue in a new chat. Save the finished sequence as a chain recipe.