You open your laptop. There's a task in front of you.
Not complicated. You roughly know what kind of result you want. But you've been handling things back to back, and your head is a bit dull — you don't want to assemble a three-line template from scratch, don't want to start thinking through the six-layer framework.
You just want something ready-made. Copy, fill in, send.
This chapter is that something.
Four templates, made concrete from the tools in earlier chapters: Stable Output (six-layer fill-in), Few-Shot Style Control, Two-Stage Method (long materials), Structured Reasoning (analysis / comparison / inference). They cover most everyday prompt situations.
But before filling in the blanks, you still have to think.
13.1 Template A: Stable Output (six-layer fill-in version)
The most general one. Anything of medium complexity or above can use it.
The value of this template isn't in anything new. It's in forcing you to think through all six slots. Most people can write the first three layers. The last three are where quality lives. Before hitting send, scan once — did I fill all six slots?
For simple tasks (one-sentence summaries, polishing, short emails), the three-line template from Chapter 5 is enough. For something more complex (organizing / rewriting / comparing / analyzing), upgrade to six layers.
13.2 Template B: Few-Shot Style Control
Use this when you need style consistency. For example, brand tone, fixed-field item writing, multi-section content with consistent style.
Two key points:
- 2 to 4 examples is best. With one example, I'll just copy it; with five or more, I start to overfit to details. The point isn't quantity — it's covering the four types: standard, variation, boundary, anti-example.
- Anti-examples need the skeleton: Element / Problem / Contrast / Suggestion. Write all four columns; only then do I know where to move from and where to move to.
If you can only pick two examples, keep Standard + Anti-example. One positive and one negative carries the most information.
13.3 Template C: Two-Stage Method (long materials)
If the material is over about two thousand words, or you've noticed that one-stage output keeps suffering factual drift or style drift, split it into two stages.
Stage 1 prompt (organize):
(Mid-process human hand-off — this is where the value of the two-stage method lives.)
You glance at the organized result. Fix a few errors, fill in a few gaps, cut a few over-inferences. Without this step, two stages degrades into "a slightly longer one stage."
Stage 2 prompt (write):
In Stage 1, don't ask for style (style instructions pull cognitive load back in). In Stage 2, don't do more analysis (if you need more material, go back and revise Stage 1). That glance during the mid-process human hand-off is where the value of the whole flow lives.
13.4 Template D: Structured Reasoning
Analysis, comparison, inference tasks — not just "give me the answer," but "tell me how you reasoned to that answer."
The key to this template is forcing the reasoning process to surface.
If I just give a conclusion, you can't tell whether I'm doing Fluent Fill-In — because looking only at the conclusion, fluent fill-in and real reasoning look almost the same. But ask me to list bases, trace them back to the material, mark confidence, and point to the dimension most likely to overturn it — and Fluent Fill-In can't hide, because if I have to point to specific locations, I have to actually go look.
13.5 How to choose a template (decision tree)
Picking among the four templates takes 30 seconds:
- Is the source material over ~2000 words? → Template C (two-stage method)
- Do you need style consistency (multiple items, brand tone, fixed fields)? → Template B (Few-Shot)
- Is it analysis / comparison / inference? → Template D (structured reasoning)
- None of the above? → Template A (six-layer fill-in)
Templates can be stacked: analysis on long material → C (organize stage) + D (write stage); long material that also needs style consistency → use B's examples in Stage 2 of C.
When in doubt, use Template A — six-layer fill-in holds up in most situations.
13.6 The limits of templates
One last thing:
Templates solve structure. Whether you'll forget to write down the format, forget to include examples, skip the judgment criteria — templates cover all of that for you.
Templates do not solve judgment:
- What the task is — you decide
- Which examples align with the style you want — you pick
- The priority order of judgment criteria — you rank
- How to handle uncertainty — you choose
The value of a template is to reduce mistakes, not to replace thinking. Paste these four templates into your notes tool as a ready-to-grab starting point — once you're fluent with them, you'll naturally grow your own variations, and that's a good thing.
What I'm most afraid of is templates being treated as a shortcut to fill-in-the-blank collaboration — that just outsources judgment to the template, and the result is that the template ends up taking your thinking away with it.
Part Three ends here.
These four chapters dealt with how long tasks stay stable. Chapter 10 first laid out the mechanism (three pieces of cognitive load + four faces of task-layer drift). The next three are the fix — Chapter 11 splits time (the two-stage method, mid-process human hand-off), Chapter 12 fills space (the six-layer framework, judgment criteria + verification flow), and Chapter 13 turns the prior two into tools (four templates, quick reference).
The three of them together are one sentence: long tasks aren't solved with a longer prompt — they're solved by splitting across time and filling across space.
Part Four moves into the rule layer. Part Three was about task-layer drift — you can handle that with prompt structure. But some things aren't in the task layer, they're in the rule layer — I'll refuse, I'll hedge, I'll suddenly turn cautious on certain topics. Those aren't fixed by writing a better prompt; but you can recognize them, you can restart, you can route around them. Let's go take a look.