12 prompt patterns that actually ship work

Prompt advice online splits into two piles: party tricks and PhD theses. Neither ships work. What ships work is a small set of reusable patterns — structural moves that turn a capable model into a reliable delegate. These twelve cover ninety percent of real professional use. Steal them verbatim; adapt the bracketed parts.

Getting better output

1. The Example Anchor

Here is an example of exactly what good looks like: [paste past output]. Produce the same for [new input]. Match structure, tone, and level of detail.

The single highest-leverage pattern in existence. One good example outperforms three paragraphs of description because it resolves a hundred silent ambiguities at once. Prevents: generic, "AI-flavored" output.

2. The Rubric First

Before writing anything: list the 5 criteria a great [deliverable] must meet for [audience]. Wait for my approval, then produce it to that rubric.

Forcing criteria before content catches misalignment when it's cheap. You edit a five-line rubric, not a five-page draft. Prevents: confident work aimed at the wrong target.

3. The Constraint Box

Constraints: exactly [N] words / [N] options. Never [X]. Must include [Y]. If a constraint is impossible, say so before starting — don't silently bend it.

Models negotiate with vague instructions and obey hard boxes. The final line is the trick: it converts silent corner-cutting into a visible question. Prevents: scope drift and quiet rule-breaking.

4. The Devil's Advocate Pass

Here is my [plan/draft/argument]. Attack it: list the 5 strongest objections a smart skeptic would raise, ranked by damage. Then tell me which one you find genuinely hard to answer.

Asking for agreement gets you agreement — models are pleasers by default. Asking for the strongest attack gets you the meeting objections two days early. Prevents: echo-chamber validation.

Getting real work done

5. The Full Brief

ROLE / TASK / INPUTS / OUTPUT / GOOD LOOKS LIKE / CONSTRAINTS / IF STUCK

The complete delegation skeleton — covered in depth in The $2 Test. Use it for anything that recurs. Prevents: under-specification, the #1 cause of agent failure.

6. The Interview Inversion

I need [outcome]. Before you produce anything, interview me: ask up to 7 questions, one at a time, until you have what you need. Then deliver.

When YOU don't know what you want, make the model extract it. It's a better requirements analyst than you are a requirements writer. Prevents: three rounds of "no, not like that."

7. The Chunked Pipeline

We'll do this in stages. Stage 1: outline only — stop for approval. Stage 2: draft section by section. Stage 3: full-document consistency edit. Never run ahead of the current stage.

Big deliverables fail as single prompts because errors compound invisibly. Stage gates keep you steering. Prevents: the 3,000-word draft that went wrong at word 200.

8. The Update, Not Rewrite

Here is the current version: [paste]. Change ONLY [specific thing]. Leave everything else character-for-character identical. Return the full updated version plus a list of exactly what you changed.

Models love to "improve" things you didn't ask about. The change-list forces honesty. Prevents: stealth edits that break something that worked.

Protecting yourself

9. The Verification Clause

Every factual claim needs a source you actually accessed. If you cannot verify something, put it under a "COULD NOT VERIFY" heading instead of stating it. Inventing a fact is a failed task.

Non-negotiable for anything numeric, legal, medical, or reputational. It doesn't make hallucination impossible; it makes it visible. Prevents: the confident invented statistic that ends up in your board deck.

10. The Confidence Split

Separate your answer into: (1) What you're confident about and why, (2) What you're guessing at, (3) What you'd need to know to be sure.

Turns a smooth, uniform-sounding answer into a map of where the solid ground actually is. Prevents: treating a guess and a fact with equal weight because they arrived in the same paragraph.

Compounding

11. The Post-Mortem Loop

Here's your output and here's my edited final version. List the differences as rules I should add to your instructions so next time needs no edits.

Your edits are training data — most people throw them away. This pattern converts them into permanent instruction upgrades. Run it three times on a recurring task and watch review time collapse. Prevents: correcting the same mistake forever.

12. The Standing Context

Read [WHO.md / VOICE.md / STANDARDS.md] before this task. They apply to everything unless I say otherwise.

The pattern that makes the other eleven cheap. Maintained context files (see The Personal AI Stack) mean you stop re-explaining yourself in every prompt. Prevents: cold-start quality on warm-start problems.

The meta-rule: if you type the same instruction twice, it belongs in a saved template or a context file — not your fingers. Prompting skill isn't creativity. It's infrastructure discipline wearing a clever disguise.

Chaining patterns: three real workflows

The twelve patterns are letters; workflows are words. Here's how they combine in practice:

The weekly report chain (patterns 12 → 5 → 8 → 11): Standing Context loads your role and standards → Full Brief runs the report generation → Update-Not-Rewrite handles your edits without collateral damage → Post-Mortem Loop converts those edits into permanent instructions. By week four, your review time drops from twenty minutes to five — measured, not vibes.
The research chain (patterns 2 → 3 → 9 → 10): Rubric First forces agreement on what a useful brief looks like → Constraint Box caps length and bans filler → Verification Clause quarantines anything unverified → Confidence Split labels the solid ground. The output is a research memo you can actually forward without triple-checking every line yourself.
The high-stakes prep chain (patterns 6 → 4 → 7): Interview Inversion extracts what you actually need for the negotiation or presentation → Devil's Advocate attacks your position until the weak joints show → Chunked Pipeline builds the final materials stage by stage with your approval at each gate. This chain is the difference between walking in prepared and walking in rehearsed.

Calibrating over time: the personal pattern file

Add a fifth context file to your stack: PATTERNS.md. Every time a prompt produces something unusually good, paste the prompt in. Every time one fails, note the failure and the fix. Within a month you'll notice your personal dialect — maybe your Example Anchors work best with two contrasting examples, maybe your Constraint Boxes need explicit "do not add caveats" lines. Generic prompt advice (including this article) is a starting point; your PATTERNS.md is the finished tool. The professionals pulling ahead don't have better prompts — they have better records of their prompts.

The anti-patterns worth naming

Three habits that quietly poison output: the personality costume ("act as a world-class expert...") — costume adjectives add confidence, not competence; state the actual standard instead. The mega-prompt — twelve instructions in one breath guarantees three get ignored; that's what Chunked Pipeline is for. The silent restart — abandoning a mediocre thread and starting fresh throws away the context you just paid to build; correct the thread instead, then Post-Mortem it. Discipline beats novelty, every week of the year.