The Simple Playbook for Prompt Chaining (Non-Technical)
✕

The Simple Playbook for “Prompt Chaining”

September 15, 2025

A practical way to get large scale, high-quality outcomes (articles, slide decks, campaigns, plans) by breaking the work into small, checkable steps that build on each other.

Why this works

Big asks often flop because they’re a pile of mixed requirements. “Prompt chaining” turns one big goal into tiny stages. Each stage:

  • repeats the essential context so it works in a fresh chat,
  • asks for one specific outcome,
  • ends with a mini checklist you can quickly verify,
  • produces a finished piece you can use or hand off immediately.

The 3-Step Method (you’ll do this repeatedly)

  1. Start a fresh chat for each stage. Paste the short “runner” prompt (below), then the stage you’re working on, and—if this isn’t the first stage—the latest file or output you’ve already got.
  2. Ask for exactly one thing. Keep it small and crisp.
  3. Check the mini checklist. If it’s off, tweak the stage and rerun. Iteration is cheap because the stage is small.

The Runner Prompt (Plain-Language)

Paste this at the top of every new stage chat:

You are a careful builder. I will give:
  1) A single “Stage” request (what to make next).
  2) (If this isn’t Stage 00) The current file/output so far.

Your job: Return a COMPLETE, USABLE result for this Stage that keeps everything
we already agreed on working the same. Prefer a SINGLE FILE unless I say
otherwise.

Rules:
  - Give only what I asked for (no extra commentary).
  - Keep earlier names/titles/labels the same unless I explicitly change them.
  - Avoid breaking past work. If unclear, make the smallest, safest choice that meets this Stage and preserves earlier behavior.
  - Before you return anything, check the acceptance checklist for this Stage.

Input format I’ll use:
STAGE:
<the Stage request goes here>

CURRENT_ARTIFACTS:
<paste/link previous output here if this is Stage 01+>

How to Write a Good Stage (Template)

Copy this and fill it in for each small step:

Stage NN — Title

Context (keep it short):
1–3 lines so this stage can stand alone (project goal, audience, tone, any non-negotiables).

Goal of this stage (one sentence):
What “done” means right now.

What to build now (requirements):

  • Concrete items the result must include (headings, sections, bullets, images, word count, voice/tone, layout rules, labels that must exist).
  • Any names/labels that must not change (titles, section IDs, filenames).
  • Constraints (keep it skimmable, 10-minute read max, uses plain language, follows brand tone).

Preserve & don’t break:

  • List fragile things from earlier stages (exact titles/labels, page order, section links).

Acceptance checklist (quick, objective checks):

  • “Top headline is exactly ‘…’.”
  • “Includes sections: Overview, 3 Key Points, Risks, Next Steps.”
  • “Max 800 words; reading level ≈ Grade 8.”
  • “Links to ‘/contact’ and ‘/pricing’ are present and work.”
  • “Previous stage’s ‘Summary’ section stays unchanged.”

Output rule:
“Return exactly one Google-doc-style Markdown file,” or “Return one single-file HTML,” or “Return a .txt outline only.” No extras.

Examples of Non-Technical Stages

A) Writing / Docs

  • 00 Outline + tone: Produce a one-page outline with headings + 1-sentence tone guide.
  • 01 First draft (Overview): Write the Overview section only; 250–400 words.
  • 02 Add ‘3 Key Points’: Three bullet sections, each 120–180 words, with bold sub-heads.
  • 03 Risks & Mitigations: One section; table with 3 rows.
  • 04 Executive Summary: 150–250 words; must stand alone.
  • 05 Line edit: Tighten for clarity and Grade-8 reading level; keep structure unchanged.

B) Slide Deck

  • 00 Skeleton: 8–10 slide titles + 1-line purpose each.
  • 01 Fill slides 1–3: Bullets only; no more than 6 per slide.
  • 02 Visual polish: Swap long bullets for diagrams/flow (describe visuals).
  • 03 Speaker notes: 3–5 sentences per slide.

C) Event/Ops Plan

  • 00 One-page brief: Goal, audience, date, success metrics.
  • 01 Run of show: Minute-by-minute schedule; contact sheet.
  • 02 Comms kit: Email invite, 3 social posts, short FAQ.
  • 03 Risk plan: 5 risks + mitigations; escalation tree.

D) Design/Brand (non-technical deliverables)

  • 00 Visual direction: 3 mood words, color swatches, font pair suggestion.
  • 01 Social post template: One 1080×1080 layout; text styles explained.
  • 02 Landing section: Above-the-fold layout; headline, subhead, CTA.
  • 03 Accessibility touch-up: Contrast and text size adjustments only.

Make It Easy to Check (Acceptance Ideas)

  • Exact phrases (headline reads exactly “…”).
  • Specific structure (these 5 sections exist, in this order).
  • Small numbers you can count (≤ 150 words, ≤ 6 bullets).
  • Plain formatting (bold/italics only; no code, no dev jargon).
  • Links work and point to the right place.
  • Regression check: “Keep the ‘Summary’ section unchanged from prior stage.”

Guardrails that Prevent Drift

  • Names & labels are sacred. (Think: headings, file names, section anchors.)
  • Keep tone and audience in every stage’s context (e.g., “busy exec, 5-minute skim”).
  • Put a mini checklist at the end of every stage.
  • If you feel scope creeping in: move extras to the next stage.

Troubleshooting (Common Fixes)

  • Came back too long/short? Add concrete word or bullet limits to acceptance.
  • Tone’s off? Paste a short voice sample and require “match this.”
  • Structure changed by accident? Add “Keep these section titles unchanged.”
  • Too much explanation? Remind: “Return only the file; no commentary.”
  • Lost earlier decisions? Paste the last accepted output under CURRENT_ARTIFACTS and call out the bits that must not change.

Quick Starter You Can Copy/Paste

Stage 00 — Outline & Voice
Context: I’m writing a short explainer for busy managers; plain English, Grade-8 reading level.
Goal: A one-page outline with clear section titles and a 2-sentence voice guide.
Build now:

  • 6–8 section headings (Overview, 3 Key Points, Risks, Next Steps, FAQ).
  • A 2-sentence “Voice & Tone” note.
  • Use short, scannable lines (no paragraph > 3 sentences).

Preserve: N/A (first stage).
Acceptance:

  • Exactly 6–8 headings listed.
  • Includes “Voice & Tone” at the end.
  • One page; no filler.

Output: Return one Markdown (.md) file only.

—

Stage 01 — Draft the Overview
Context: Keep the Stage 00 outline and voice.
Goal: Write the Overview section only (250–350 words).
Build now:

  • Start with a one-sentence promise statement.
  • 2–3 short paragraphs max.
  • Bold one key sentence.

Preserve: Section titles from Stage 00 unchanged.
Acceptance:

  • Word count within 250–350.
  • First sentence is a clear promise.
  • Exactly one bolded sentence.
  • Other sections remain as placeholders.

Output: Return one Markdown (.md) file with the full outline and the new Overview filled in.

—

Stage 02 — Add “3 Key Points” Sections
Context: Keep the Stage 00 outline and the approved Overview from Stage 01. Audience is non-technical; plain English.
Goal: Draft the three “Key Points” sections that expand on the main idea.
Build now:

  • Write three sections named exactly as in the outline (don’t rename).
  • Each section: 120–180 words, skimmable, with one bold subhead in the first sentence.
  • Use short sentences; avoid jargon.

Preserve: Overview and all section titles from earlier stages.
Acceptance:

  • Exactly three sections added, titled as per Stage 00.
  • Each section is 120–180 words and contains one bold subhead in sentence 1.
  • The Overview text remains unchanged.

Output: Return one Markdown (.md) file with the Outline, Overview, and three Key Points completed.

—

Stage 03 — Risks & Mitigations
Context: Same audience and tone. We now add a practical risk table.
Goal: Add a “Risks & Mitigations” section with a simple 3-row table.
Build now:

  • Section heading exactly “Risks & Mitigations”.
  • Markdown table with 3 rows: Risk, Why it might happen, Mitigation.
  • Keep rows brief and actionable.

Preserve: All prior sections and headings unchanged.
Acceptance:

  • Section title is exactly “Risks & Mitigations”.
  • Table has 3 rows and the 3 named columns above.
  • No edits to Overview or Key Points.

Output: Return one Markdown (.md) file with the new section appended.

—

Stage 04 — Executive Summary
Context: For busy execs; must stand alone at the top of the document.
Goal: Add a concise Executive Summary that previews the whole piece.
Build now:

  • Insert a section titled “Executive Summary” above “Overview”.
  • 150–250 words, 2–4 short paragraphs, no jargon.
  • One sentence should bold the core takeaway.

Preserve: All other section titles and content unchanged.
Acceptance:

  • Appears before “Overview”.
  • 150–250 words total.
  • Exactly one bolded takeaway sentence.

Output: Return one Markdown (.md) file with Executive Summary added in the right position.

—

Stage 05 — Line Edit for Clarity
Context: Final readability pass for non-technical readers.
Goal: Tighten language, keep structure and labels unchanged.
Build now:

  • Shorten long sentences, swap jargon for plain words.
  • Keep all headings, order, and labels identical.
  • Minor punctuation/grammar fixes only.

Preserve: Section names and order (don’t change anchors or links).
Acceptance:

  • Reading level ≈ Grade 8 (short sentences, simple words).
  • All section titles unchanged and in the same order.
  • Total word count within ±10% of Stage 04.

Output: Return one Markdown (.md) file—the final, clean draft.

Thanks

Thanks to MP and NL for reading drafts of this.
© MMXXV RMK · Null Space (0x00 0xA0)