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.
The strongest version of this chapter here starts one step further back: use Deep Research as link one, so the chain begins from a sourced report rather than from recollection, and the [check] marks in the book become links you can open. The middle links then work as the book describes, in ordinary chat. Where Workspace earns its place is at the end - the approved draft exports to Google Docs, which is where a leaflet or a plan should live when other people have to read, comment on and print it. A chain you run every month belongs in a Gem, so the steps and the stop-and-wait rule are standing instructions rather than something you retype.
From the book Use Deep Research as a strong first link, then ask Gemini to outline and draft from that report. Export the approved draft to Google Docs for the final polish; the same chain of prompts works on all three platforms.
- Use Deep Research as link one, then compress it to a baton summary.
- Do not pass the full report forward - the draft will inherit its padding.
- Export only the approved draft to Docs; later chat edits will not follow.
- Have a native speaker check translated leaflets before printing.
- Keep a monthly chain as a Gem, stop-and-wait rule included.
Instead of
Write a business plan for our SHG pickle business.
Gemini version
Twelve of us, a self-help group near Warangal, starting a small pickle business. Four steps lie ahead - shortlist, outline, plan, Telugu - and I want step one alone. Begin with Deep Research on one question only: which pickles can be made from produce grown around Warangal, what the raw material costs per kilo at present, how long each keeps without refrigeration, and what a unit our size must register for before it can sell. Keep the report short and give me pages I can open. [Attach photographs of what is actually selling in your weekly market, if you have them.] Tell me which of these you can see in my photographs - what is in front of me beats what is popular nationally. Then build the five candidates into a Google Sheet called "Pickle costing", one row per pickle, columns for cost per kilo, keeping time, ease of local sale and the source of each figure. We will update those rates ourselves every month as the market moves, which is why it needs to be a sheet and not a message. Leave blank any cell you could not source rather than filling it with a guess. Say which figures are guesses if you make any. Stop at the sheet. We will choose three and come back.
Then loop it
- Compress that report to under 200 words - the five candidates, the sourced figures, the registration requirement, nothing else. We have chosen mango, gongura and lemon.
- Using that summary and those three alone, outline the one-page plan: products, costs, division of labour, where we sell, first-month target. Carry nothing else over from the report. Stop at the outline.
- Right, with "where we sell" at the top. Write the full one-page plan in simple English and export it to Google Docs, where the group can read it together. Then give me a simple spoken Telugu version in the chat for reading aloud at the meeting, rupee figures left as numerals.
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.
Gemini version
Budget-travel channel, Hindi-English. Ten minutes on doing Gulmarg from Srinagar and getting back the same evening. Four steps ahead of us; this is the first. [Attach your photographs or clips from the last trip up.] Start by telling me what my own footage already covers, and what I will have to shoot again. Then ground in Search the four things that decide whether a viewer's day goes well - the ropeway, the money, the cold, and the timing of the return journey - and give me twelve lines I could say on camera, each with the page you took it from. Anything you cannot source to this season, write [check] beside it and name who I should telephone in Srinagar: the ropeway office, the taxi union, the tourism department. Those calls are mine to make and I will make them before a word is scripted. No outline yet, no script, no titles. Twelve lines and the gap list.
Then loop it
- I rang around - 4 and 11 were wrong and are gone. From facts 1, 3, 5, 7 to 10 and 12, build a scene-by-scene outline for ten minutes with timings. No searching this round.
- Outline approved. Write the full script in casual Hinglish with B-roll notes in brackets, then export it to Google Docs so I can read it off the laptop while shooting.
- From the exported script, 5 title options under 60 characters and a 150-word description with chapter timestamps. For the titles alone, check Search for how other Gulmarg videos are currently titled and tell me which of my five is too close to one that already exists.
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.
Gemini version
We build this in four passes and I will not accept an early draft. Pass one is below. Ground everything here in Search, keeping to the bodies our health centre itself answers to: Pune Municipal Corporation, then the national vector-borne disease programme, then WHO. Begin with the corporation. Does PMC put out its own monsoon advisory for residents? If it does, link it and show me where our page must not contradict it - agreeing with the corporation serves us better here than sounding original. While you are there, find the current municipal number for reporting water that has been standing, from an official page rather than a news report. Then give me eight things a family can do to deny mosquitoes a puddle around the house. Plain words, each line carrying its link and the body that recommends it. One limit holds throughout: we are showing people how to keep water from collecting, not how to treat anybody. If a page runs the two together, return the first half and say what you set aside. Our single clinical line is settled already - "see a doctor if fever continues". Where those three bodies stress different things, show me the disagreement and say which a Pune colony should follow. Put the eight into a Google Doc called "Leaflet - messages" and share it with our coordinator, so comments land in the margin instead of on WhatsApp. Then wait.
Then loop it
- Health centre has cleared tips 1 to 6 and added "empty flower-pot trays every week". From those 7, write the leaflet: headline, 7 short points, closing line with a space for [helpline number]. Do not search this round.
- Export it to Google Docs and share it with our coordinator so she can comment in the margin. Alongside that, give me a compact baton summary - aim, audience, the 7 cleared tips, the scope rule, the tone - to carry into a fresh chat for translation.
- (New chat.) [Paste the baton summary and the leaflet.] Put this into simple spoken Marathi for colony residents: same headings, same order, [helpline number] untouched. Then name the two or three Marathi lines that could be misread as medical advice, so our native-speaking volunteer reads those first.
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.