Skills update

This commit is contained in:
2026-07-01 13:44:00 -05:00
parent 3d5e97c1e1
commit 8b6dae8181
2 changed files with 65 additions and 0 deletions

View File

@@ -109,6 +109,14 @@ Propose a scene-by-scene plan:
- Opening hook and closing beat
- Timeline placement (what day, what bells) — cross-reference with `timeline-book{BOOK}.md`
**Callback pass (BOOK ≥ 2 only):** Consult the Key Callbacks table in `chapters/book{BOOK}/CLAUDE.md` and this chapter's entry in `outline/book{BOOK}-outline.md`. List every prior-book reference the scene plan will land. For each, classify:
- **Inline backfill** — a new reader needs a one-sentence Phelan-voice reminder. Mark which scene carries it.
- **Texture only** — name drop or atmosphere; no backfill needed.
- **Intentionally opaque** — institutional/thriller opacity is the point. Note that choice is deliberate.
Present the classification to the author alongside the scene plan. Opaque choices need explicit approval. If `BOOK == 1`, skip this pass.
**Wait for author approval before proceeding to Stage 3.**
## Stage 3: Draft
@@ -158,6 +166,9 @@ Before writing scenes involving these elements, consult:
- Named location details → `world/locations/{name}.md`
- Magic system usage → `world/magic/runic-flow-rules.md` and `world/magic/exploits-log.md`
- Prior chapter state → `world/story-summary-book{BOOK}.md`
- Prior-book callbacks (BOOK ≥ 2) → `chapters/book{BOOK}/CLAUDE.md` Key Callbacks table + `world/story-summary-book{N}.md` for each prior book. Apply the Stage 2 callback classification: write the inline backfill sentence where planned, using Phelan's established backfill patterns (functional explanation without source attribution; consequence-driven reference; carrier character encoding history).
**Inline backfill length cap:** one sentence, Phelan's voice, no source attribution ("the Floundry job," not "in Book 1 I…"). If a callback needs more than one sentence, the Stage 2 scene plan should have flagged it as a dedicated beat, not inline.
When uncertain, mark `[CONTINUITY FLAG: note]` inline rather than guessing.
@@ -174,6 +185,7 @@ Before saving the draft and telling the author it's ready, run this pass:
3. **Paragraph-opener scan:** Read only the first few words of each paragraph. Flag any cluster of identical openers.
4. **Continuity scan:** Verify any time references, currency amounts, character-knowledge claims, and location details against the canonical files listed in the continuity pre-check.
5. **Crutch construction scan:** Search the chapter for the construction templates above. Trim any that cluster.
6. **Callback scan (BOOK ≥ 2):** For every prior-book reference in the draft, confirm it matches the Stage 2 classification. Add any missed callbacks to the list and either backfill (one sentence, Phelan-voice, no source attribution) or flag as deliberately opaque.
Fix issues before handing off. The less manuscript-analysis finds post-hoc, the better.
@@ -196,6 +208,7 @@ The author has edited `chXX-draft.md`. Now perform a final review focused on:
- Crutch constructions over quota (*"X the way Y [verb] X"*, anaphoric *"It was [noun] of someone who…"* pairs, *"The X was not X. The X was X…"* architecture, *"I did not X. I did not Y…"* clusters, *"Not X. Not Y."* opener counts)
- Paragraph-opener clusters (3+ consecutive paragraphs with the same opener)
9. **Noise parenthetical discipline** — verify count within target (46 establishing, 35 ongoing) and that each does narrative work; flag any consecutive parentheticals not demanded by pacing (hyperfocus, crash, action spike)
10. **Callback handling (BOOK ≥ 2)** — for each prior-book reference in the chapter, verify it matches its Stage 2 classification. Inline-backfill callbacks must read cleanly for a reader who has never seen the prior book; opaque callbacks must be deliberate, not accidental. Flag any unclassified callback that slipped in during drafting.
**Output format:** Present findings organized by category. For each issue, quote the relevant text and suggest a fix. After author approval of any changes, **rename** `chXX-draft.md` to `chXX-final.md` using `mv` — do NOT rewrite the file contents.