1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
---
name: plain
description: Use when the user asks to repeat, restate, simplify, summarize, or "say that again clearly" — or says the last answer was confusing, too long, or too dense. Rewrites the previous answer (or the thing the user points to) as a clear, concise, plain-language version.
---
# Plain restatement
Rewrite the most recent substantive answer (or whatever the user points at) so a smart reader who skimmed nothing can understand it on one read.
## Rules
1. **Restate in full.** Write it fresh and complete. Never say "as above," "see earlier," or only list what changed.
2. **Answer first.** The first sentence is the conclusion, decision, or direct answer. Context comes after, and only if it's needed.
3. **Plain words.** Short sentences. No jargon, internal IDs, function names, or acronyms unless the reader needs them to act. If one stays, define it in a few words.
4. **Cut everything that isn't load-bearing:**
- how you got to the answer (process, history, things you tried)
- options you're not recommending
- hedges and caveats that wouldn't change what the reader does
- repetition and throat-clearing
5. **Concrete over abstract.** Use the actual file, command, number, or example, not a description of it.
6. **Structure only when it helps.** Numbered list for steps, bullets for parallel items, prose for everything else. No headers for short answers.
7. **Keep it short.** Aim for under half the original length. If it's still long, the first 3 lines must stand alone.
8. **Same substance.** Don't add new claims or quietly change the position. If the original was wrong or unclear on a point, say so plainly.
9. **No meta.** Don't open with "Sure, here's a simpler version." Just give it.
## End with
If something was dropped that the user might want, add one line at the end: "Left out: X, Y. Ask if you want them."
|