# My 7-step prompt chain failed silently at step 6. Here's what replaced it. > Source: > Published: 2026-06-24 01:06:34+00:00 A manual checkpoint outperformed full automation by 35 percentage points. That's the number that changed how I build every prompt chain now. I spent two months convinced longer chains meant better output. More refinement steps, closer to correct. So I built a 7-step chain for client ad copy — brief intake, angle extraction, brand voice filter, headline drafting, scoring, rewriting, final polish — all automated via Claude Sonnet, each output feeding the next. It worked for two days. Then a client brief came in with an ambiguous audience definition. The angle-extraction step produced garbage, everything downstream inherited it, and because nothing interrupted the chain, I didn't catch the failure until step 6. Burned tokens, burned time, nothing usable. The fix wasn't a better prompt. It was a shorter chain with me reading the output in the middle. I rebuilt it as two calls with a manual gate between them. Step one extracts structure — audience, offer, constraints, tone. I read that output. If something's off, I edit it in place, which takes about 30 seconds. Then step two gets the corrected structure and generates headline variants and a body draft. I tracked this across 11 client accounts for six weeks. Usable first drafts went from roughly 40% to around 75%. The gate was the entire reason — not the prompts themselves. The other pattern worth stealing immediately: role-locked single-purpose prompts. I used to write long multi-instruction prompts asking Claude to extract, evaluate, and rewrite in one call. Mediocre across all three. Now each call gets one job and a locked role at the top: ``` You are a direct-response copywriter reviewing this for offer clarity. Do nothing else. ``` Separate call, separate role for brand voice. More API calls, higher cost per piece — but on the third or fourth piece in a batch, a combined prompt starts drifting in emphasis in ways a single-purpose prompt doesn't. I wrote up the full breakdown — including the Obsidian staging buffer setup that added 4 minutes per piece and measurably cut revision time, plus the failure log pattern I stumbled into that uses bad outputs as prompt input — over on dailyfocusmag.com.