Sprint 56: Upstream draft control and editorial boundary refactor

- book_chapter: Remove PASS 2+3 (internal polish cycle); replace with narrow
  SELF-CHECK step (structural validation only — names/POV/hook/format/word-floor).
  Add anti-overpolish drafting discipline rules to PASS 1.
  Add genre-aware guide-use note (apply only the guide matching {genre_name}).
  Update adjudication prose_quality description to match draft-quality standard.

- chapter_polish: Convert from broad 'Rewrite the chapter' pass to bounded
  editorial control pass. Explicitly forbids expansion, sensory addition,
  global voice upgrades, new content. Instructs verbatim preservation of
  unaffected paragraphs. Adjudication rewritten around correction fidelity
  rather than 'more polished is better'. Threshold lowered from 90 to 80.

- chapter_review: Add explicit output categories — STRENGTHS TO PRESERVE,
  MUST-FIX CONTINUITY, MUST-FIX CLARITY, OPTIONAL, FORBIDDEN, VERDICT.
  Remove 'REWRITE' verdict option (roundtable resolves that). Remove all three
  writing-craft guides (editorial tasks do not need genre writing guidance).

- chapter_roundtable: Update CONSENSUS REACHED block to MUST APPLY / OPTIONAL /
  PRESERVE / VERDICT categories. Require disagreements to be resolved before
  calling consensus. Remove REWRITE verdict option. Remove all writing-craft
  guides. Remove 'skills' from sections. Add package hint to populate key_changes
  from the full structured consensus. Update adjudication to score structured output.

- book_outline: Strengthen Voice & Tone Guide as hard operating constraints
  (not aspirations); include anti-overpolish rules, rhythm rules, and voice
  don'ts. Expand per-chapter outline format to include Opens-at location,
  Character state, and Dominant tension. Enrich chapter task description
  packets with that state data so book_chapter has richer upstream context.

- skills/skills.md: Document writing-vs-editorial guide split established in
  Sprint 56. Update Used-by column. Add boundary rules section.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-21 16:34:05 -04:00
parent 9ac0fa98b7
commit 87c01864dc
6 changed files with 272 additions and 86 deletions

View File

@@ -1,5 +1,5 @@
name: book_chapter
description: "Write one chapter — continuity check, draft, deepen, then spawn editorial review."
description: "Write one chapter — continuity check, draft, self-check, then spawn editorial review."
debug: true
system: agent_prompt
@@ -15,6 +15,11 @@ skills:
- guides/RomanceFictionGuide.md
- guides/SciFiFictionGuide.md
# Genre-aware guide use: All three genre guides are injected so this template
# can serve any fiction genre. Apply ONLY the guide that matches {genre_name}.
# Ignore guides for other genres — conflicting craft signals from non-matching
# genres will degrade the chapter. The active genre is always {genre_name}.
agent_prompt:
- "= identity.md"
- "agent.rag.json"
@@ -32,12 +37,15 @@ sections:
steps:
- type: think
hint: |
PASS 0 — BIBLE & CONTINUITY PLAN (produce a PLAN only — do NOT write chapter prose yet)
PASS 0 — BIBLE, CONTINUITY, AND DRAFT PROMPT
GENRE: {genre_name} | AUDIENCE: {genre_audience}
PROSE STYLE GUIDE: {prose_style}
TARGET CHAPTER LENGTH: ~{chapter_target_words} words
⚠️ SKILLS & GUIDES NOTE: You have multiple genre guides available.
Apply ONLY the guide that matches {genre_name}. Ignore guides for other genres.
CONTINUITY GUARDRAILS:
- Use ONLY the outline / character bible and the immediately previous chapter for continuity.
- Ignore future chapters, editorial reviews, roundtables, polish drafts, and any non-chapter artifacts.
@@ -67,8 +75,8 @@ steps:
Label them: "PREVIOUS CHAPTER ENDED WITH: ..."
Your new chapter MUST pick up from this exact moment.
STEP 4 — CHAPTER PLAN:
State your plan — do NOT write prose yet:
STEP 4 — BUILD THE DRAFT PROMPT:
Write the exact drafting prompt for the next pass. That prompt must include:
- CHAPTER: Exact chapter number and title (from the task message)
- POV CHARACTER: Whose perspective are we in?
- FIRST LINE: The exact opening sentence, continuing from the previous ending
@@ -76,15 +84,18 @@ steps:
- CHAPTER GOAL: What plot event MUST happen here?
- KEY BEATS: 35 numbered scene beats that will form the chapter
- CLOSING HOOK: Exact last image or line that makes readers continue
- Reminders about continuity, prose style, and target length
Stop here. Output ONLY the plan above. The full chapter will be written next.
Stop here. Output ONLY the draft prompt. Do NOT write chapter prose yet.
- type: think
model: power
hint: |
PASS 1 — WRITE THE FULL CHAPTER
PASS 1 — WRITE THE DRAFT
Using the plan from your previous step, write the complete chapter now.
Use the draft prompt below as your exact writing brief:
{steps[0].text}
Requirements:
- Start with the FIRST LINE you planned — make it continue naturally from the previous chapter
@@ -100,21 +111,73 @@ steps:
writing — add interiority, sensory detail, extended dialogue beats, and scene transitions
until you hit the target. Short chapters will be REJECTED in adjudication.
Output ONLY the polished chapter text.
DRAFTING DISCIPLINE — apply these on every page:
- {prose_style} is a hard constraint, not decoration
- Not every paragraph needs a memorable or quotable line — use functional connective prose
- Let observation precede interpretation: show the moment before naming what it means
- Avoid clustering aphorisms or thesis-style sentences back to back
- Prefer scene motion over thesis delivery — action and dialogue carry meaning
- Write ONE complete draft now. Do NOT self-polish. Reviewers will give feedback downstream.
Output ONLY the draft chapter text.
Start directly with the chapter title (e.g., "Chapter N: [Title]") and opening line.
No commentary, no plan headers, no "Pass 1" label.
- type: think
hint: |
SELF-CHECK — STRUCTURAL VALIDATION ONLY
You have just written a chapter draft. Your job here is narrow: check the draft against
the structural checklist below, apply ONLY the corrections that fall within scope, and
output the final chapter.
DRAFT TO CHECK:
{steps[1].text}
CHECKLIST — check each item, note any issue found:
1. BEAT & HOOK: Does the chapter reach its intended emotional beat and closing hook
from the PASS 0 draft prompt? Flag if the chapter ends without the planned hook.
2. NAMES & POV: Are all character names and the POV consistent with the bible/outline?
Flag any name that doesn't match the project canon.
3. CONTINUITY TERMS: Do world rules, place names, and timeline references match
project state? Flag any factual break.
4. FORMATTING: Are there obvious section-break artifacts, duplicate headers,
or missing chapter title? Flag and fix.
5. WORD FLOOR: Is the draft within 10% of {chapter_target_words}? Flag only if
critically short (more than 20% under target) — do not expand for style.
ALLOWED CORRECTIONS:
- Fix a wrong character name to match the canon name
- Fix a POV slip (e.g., the chapter is 1st-person but one paragraph shifted to 3rd)
- Fix a missing or duplicated chapter title/header
- If the chapter is missing its closing hook entirely, add it as a final paragraph
that matches the hook specified in the draft prompt — no new invention beyond the
planned hook
NOT ALLOWED — do not make any of these changes:
- Improve any sentence for prose quality, rhythm, or lyricism
- Deepen emotional beats or add interiority
- Expand any description or add sensory detail
- Reorder scenes or restructure the chapter
- Add new metaphors, aphorisms, or quotable lines
- Normalize or upgrade the authorial voice
Output the FINAL CHAPTER (corrected where structurally required, verbatim everywhere else).
Start directly with the chapter title and first line.
No preamble, no validation notes, no commentary — ONLY the chapter text.
- type: document
filename: "chapter-{chapter_ref}"
- type: package
hint: |
The chapter has been written and committed.
The draft chapter has been written, self-checked, and committed.
CRITICAL — include the `chapter_text` field:
Copy the COMPLETE chapter text you just wrote into the `chapter_text` field.
Copy the COMPLETE chapter text from the self-check output (step 2 — the final chapter draft)
into the `chapter_text` field.
Reviewers have NO other way to access the chapter content.
Do NOT summarize or truncate it — include every word of the final chapter.
Do NOT summarize or truncate it — include every word of the chapter.
Now spawn the three independent editorial reviewers
and the roundtable debate. Use the exact task_names shown — the roundtable depends_on all three.
@@ -166,6 +229,7 @@ steps:
genre_name: "{genre_name}"
genre_audience: "{genre_audience}"
chapter_ref: "{chapter_ref}"
chapter_target_words: "{chapter_target_words}"
depends_on:
- "Review (Devon): {chapter_ref}"
- "Review (Lane): {chapter_ref}"
@@ -190,7 +254,7 @@ adjudication:
description: "Characters are distinct and consistent"
prose_quality:
weight: 15
description: "Writing is polished and engaging"
description: "Writing is clear and readable; voice is consistent with {prose_style}"
continuity:
weight: 10
description: "Consistent with prior chapters and canon"