|
1 | 1 | # Stage: draft |
2 | 2 |
|
3 | | -Write the piece. This is where the voice guide does its heaviest work — the draft should sound, read, and look like Jeff wrote it, not like a competent stranger did. |
| 3 | +Write the piece. This is where the voice guide does its heaviest work — the draft should sound, read, and look like the author wrote it, not like a competent stranger did. |
4 | 4 |
|
5 | 5 | ## Read first |
6 | 6 |
|
7 | 7 | - The brief at `brief:<path>` — audience, purpose, one job, thesis, medium. |
8 | 8 | - The outline at `outline:<path>` — the section order and per-section ideas. |
9 | | -- The **entire** voice guide. Every section applies now. |
| 9 | +- The **entire** voice guide. Every section applies now. The guide is the sole |
| 10 | + source of voice rules — do not rely on remembered rules from previous |
| 11 | + versions of this skill or from other drafts; the guide compounds and old |
| 12 | + rules get overturned. |
10 | 13 |
|
11 | | -## Draft against the guide, deliberately |
| 14 | +## Pull the exemplars |
| 15 | + |
| 16 | +Identify the piece's register band from the brief using the guide's register |
| 17 | +section (expressive / analytical / formal / technical). If a `rotunda` MCP |
| 18 | +connection is available, call `voice_exemplars` with that register and keep the |
| 19 | +returned pairs in view while drafting: each pair shows the same content as a |
| 20 | +competent generic model wrote it and as the author actually wrote it. **Write |
| 21 | +like the author side of the pairs.** The pairs quote private documents — never |
| 22 | +copy them into the draft or into public files; they are reference only. |
12 | 23 |
|
13 | | -Do not write generically and hope it sounds like Jeff. Write *toward* the guide: |
| 24 | +Without the MCP connection, proceed on the guide alone and note the gap in the |
| 25 | +run output. |
14 | 26 |
|
15 | | -- **Lead with the governing idea** (§2.1, §6). The first lines state the thesis. No runway, no throat-clearing. |
16 | | -- **Reach for Jeff's verbs** (§5): narrow, collapse, absorb, land, resolve, gate, ship, cut. Plain Anglo-Saxon over Latinate abstraction. |
17 | | -- **Use the signature moves where they fit** (§3) — but earn them, don't sprinkle them: |
18 | | - - the triad (group into threes), |
19 | | - - the aphoristic clincher to close a section, |
20 | | - - the em-dash sharpener with a concrete example, |
21 | | - - the framing-question header with a stakes parenthetical, |
22 | | - - the stakes sentence ("if no one owns it, X silently fails"), |
23 | | - - the "X, not Y" reframe, |
24 | | - - honesty markers (⚠, "ruled out:") instead of hedging. |
25 | | -- **Vary sentence length hard** (§4). Long, clause-stacked sentence, then a short hammer. Deliberate fragments are allowed. Read each paragraph aloud in your head; if it drones or you run out of breath, re-cut before moving on. |
26 | | -- **Match the medium profile** (§8): essay = voice-forward, a clincher per section; doc = Summary → Evidence → Why-it-matters skeleton, concrete numbers, minimal adjectives; email = open with the ask or answer, one screen, end with the single next action. |
27 | | -- **Format for the skim** (§7): framing-question or noun-phrase headers, bold inline labels for category list items, short paragraphs, tables where data is parallel, ⚠ for uncertain claims, functional emoji only. |
28 | | -- **Use the right term of art once** (§9), matched to the audience in the brief. Define on first use only if that reader might not know it. |
| 27 | +## Draft against the guide, deliberately |
29 | 28 |
|
30 | | -## Kill on sight while drafting (§5, §10) |
| 29 | +Do not write generically and hope it lands. Write *toward* the guide: identify |
| 30 | +the register band first and apply that band's rules, reach for the signature |
| 31 | +moves where they fit (and only where they fit — the guide's anti-pattern list |
| 32 | +names the manufactured versions), and honor the guide's rhythm and formatting |
| 33 | +sections. Read each paragraph aloud in your head; if it drones, re-cut before |
| 34 | +moving on. |
31 | 35 |
|
32 | | -Do not draft these in the first place: `delve`, `tapestry`, `realm`, `landscape`, `leverage` (verb), `utilize`, `robust` (as filler), `seamless`; the inflation construction **"not just X — it's Y"** (distinct from the *allowed* sharp "X, not Y"); throat-clearing openers; hedges (`honestly`, `arguably`, `somewhat`); empty intensifiers (`very`, `really`). The panel will catch these, but a clean first draft saves a review round. |
| 36 | +The architecture matters more than the words. The measured failure mode of |
| 37 | +model drafts is structural: sentences welded long, one-beat paragraphs merged |
| 38 | +away, questions answered instead of left standing, transitions announced |
| 39 | +("I bring this up because…") instead of made. Check the shape of what you |
| 40 | +just wrote, not only its vocabulary. |
33 | 41 |
|
34 | 42 | ## Procedure |
35 | 43 |
|
36 | | -1. Read brief, outline, and the full voice guide. |
| 44 | +1. Read brief, outline, the full voice guide, and the register's exemplars. |
37 | 45 | 2. Write the complete draft — every section from the outline, no placeholders. |
38 | | -3. Do one self-pass against §5 and §10 before handing off: cut the slop you can already see. |
39 | | -4. Write `draft.md`. This file is revised in place during the review loop, so write it as the working copy. |
| 46 | +3. Self-pass against the guide's diction kill-list and anti-pattern section: |
| 47 | + cut the slop you can already see. |
| 48 | +4. **Lint the architecture.** If the `rotunda` MCP connection is available, |
| 49 | + call `voice_lint` with the draft and the register. `pass` or `borderline` |
| 50 | + hands off; on `fail`, restructure toward the flagged metrics (sentence mix, |
| 51 | + paragraph pacing, questions, punctuation habits — not word swaps) and lint |
| 52 | + once more. Include the final verdict in the run output. Without the |
| 53 | + connection, skip and note it. |
| 54 | +5. Write `draft.md`. This file is revised in place during the review loop, so |
| 55 | + write it as the working copy. |
40 | 56 |
|
41 | 57 | ## Output: draft.md |
42 | 58 |
|
43 | | -The finished prose, in the target medium's format. No meta-commentary, no "here is the draft" preamble — the file is the piece. Lead with the governing idea on the first line. |
| 59 | +The finished prose, in the target medium's format. No meta-commentary, no |
| 60 | +"here is the draft" preamble — the file is the piece. Lead with the governing |
| 61 | +idea on the first line. |
44 | 62 |
|
45 | 63 | ## Voice-guide sections this stage leans on |
46 | 64 |
|
|
0 commit comments