claude_skills/chapter-workflow/SKILL.md

name, description

name	description
chapter-workflow	Use when starting a new chapter, resuming chapter drafting, or moving to the next stage of chapter development for A Phelan Varrant Novel. Invoke with a chapter number argument, e.g. /chapter-workflow 3

Chapter Workflow

5-stage pipeline for developing chapters. Invoke with chapter number: /chapter-workflow 3

Stage Flow

digraph chapter_flow {
    rankdir=TB;
    node [shape=box];

    detect [label="Detect book + stage\nfrom existing files" shape=diamond];
    seed [label="Stage 1: Seed\nConfirm chXX-input.md exists\nand has content"];
    breakdown [label="Stage 2: Scene Breakdown\nRead input + summary + outline\nPropose scene plan"];
    draft [label="Stage 3: Draft\nWrite full chapter\ninto chXX-draft.md"];
    revision [label="Stage 4: Review\nAuthor edits, then Claude reviews\nclarity/grammar/flow"];
    continuity [label="Stage 5: Continuity\nUpdate world/character files\n+ story summary + timeline"];

    detect -> seed [label="no input file"];
    detect -> breakdown [label="input exists, no draft"];
    detect -> draft [label="draft in progress"];
    detect -> revision [label="draft complete"];
    detect -> continuity [label="final exists"];

    seed -> breakdown;
    breakdown -> draft;
    draft -> revision;
    revision -> continuity;
}

On Invoke

Parse chapter number from args (default: ask). Set XX = zero-padded number.

Detect Book Number

Determine which book we're working on by checking the chapter directory path:

• Look for chapters/book{N}/chXX-input.md — the {N} is the book number
• If the user has a chXX-input.md open in the IDE, derive the book number from its path
• If ambiguous, check which chapters/book{N}/ directories exist and ask the user
• Set BOOK = detected book number (e.g., 1, 2, 3)

All subsequent file references use book{BOOK} instead of hardcoded book1.

Key Context Files (per book)

These files provide continuity context. Read the story summary and timeline instead of re-reading prior chapter drafts:

File	Purpose
world/story-summary-book{BOOK}.md	Running summary of all prior chapters — characters, events, plot threads, financial state. Primary context source.
world/timeline-book{BOOK}.md	Bell/time references, day-of-week tracking, elapsed time. Check before writing any time reference.
chapters/book{BOOK}/CLAUDE.md	Book-specific premise, themes, milestone beats
outline/book{BOOK}-outline.md	Chapter-by-chapter outline
world/magic/exploits-log.md	All exploits used (cross-book)

Detect Stage

Check which files exist in chapters/book{BOOK}/:

Files Present	Stage
No chXX-input.md	Create from template, ask author to fill it
chXX-input.md only	Stage 2: Scene Breakdown
chXX-input.md + partial chXX-draft.md	Stage 3: Resume/complete draft
chXX-input.md + complete chXX-draft.md	Stage 4: Author edits, then review
chXX-final.md exists	Stage 5: Continuity update

Stage 1: Seed

If chXX-input.md doesn't exist:

1. Read context sources for this chapter. Prefer the outline file as the primary source of chapter-level detail; fall back to the book CLAUDE.md only if the outline is absent or thin:

   • outline/book{BOOK}-outline.md — primary source. Find this chapter's row in the chapter table AND any dedicated per-chapter section for planned-but-not-drafted chapters. Extract plot beats, scene-level content, and the Arc Intersection Map row for this chapter number to capture which character arcs advance.
   • chapters/book{BOOK}/CLAUDE.md — secondary source. Look for the chapter in any Chapter Breakdown or Character Arcs section if present. Modern lean CLAUDE.md files point to the outline for this content — in that case, the CLAUDE.md provides Premise, Themes, Milestone Beats, Key Callbacks, and Character Arcs one-line shifts for orientation, not per-chapter detail.
   • Relevant character files from characters/ — for each character with a scene in this chapter, read the Book {BOOK} progression table and any milestone entries landing near this chapter number. This catches voice, dialog patterns, and current relationship state.

2. Create chXX-input.md using the template from chapters/chapter-input-template.md (central location, shared across all books), but pre-populate it with the extracted context:

   • Scene Goals: Fill with the plot beats, case developments, and milestone beats from the outline's chapter entry. Use bullet points.
   • Character Moments: Fill with character arc beats, relationship developments, and the Arc Intersection Map row for this chapter. Pull specific voice/behavior notes from the character files where relevant.
   • Mood / Tone: Fill with any tone/pacing notes derivable from the chapter description (e.g., "tension building," "quiet domestic," "action climax").
   • Key Dialog and Freeform Notes: Leave these as empty template sections (HTML comments only) — these are for the author's original input.

3. Tell the author the input file has been seeded with context from the outline (and, where applicable, the book CLAUDE.md and character files). Ask them to review it, add their dialog ideas and freeform notes, and re-invoke when ready.

If chXX-input.md exists but ALL sections are empty (only HTML comments), tell the author it needs content before proceeding.

Stage 2: Scene Breakdown

Read these files for context:

• chapters/book{BOOK}/chXX-input.md — author's notes for this chapter
• world/story-summary-book{BOOK}.md — prior chapter context (DO NOT re-read full chapter drafts)
• world/timeline-book{BOOK}.md — timeline and time references
• outline/book{BOOK}-outline.md — chapter outline
• chapters/book{BOOK}/CLAUDE.md — book-specific instructions
• world/magic/exploits-log.md — exploits used so far
• Relevant character files from characters/ (check story summary for which characters are active)

Propose a scene-by-scene plan:

• Number of scenes with estimated word counts
• What each scene accomplishes
• Where input dialog and character moments slot in
• 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

Write the full chapter in one pass based on the approved scene plan. Save to chXX-draft.md.

Before drafting: Re-read the story summary and timeline to ensure continuity. Do NOT re-read full prior chapter drafts — the summary contains everything needed.

Also re-read the character files for every character with a speaking or on-page role in this chapter. The character files in characters/ are the canonical source for:

• Voice quirks and dialog patterns (e.g., Phelan's noise parentheticals, Mere's declarative speech and three-stream limit, Ledger's architectural expressions, Devod's ten-ideas methodology, Kae's pendant tell, Leon's post-Ch18 shift)
• Current relationship state (partner, enemy, estranged, newly reclassified)
• Physical description, bearing, and signature mannerisms
• Recent character development that may not be captured in the scene plan

The scene plan from Stage 2 carries forward what happens; the character files carry forward how each character sounds and behaves while it happens. Both are required for draft fidelity.

Process:

1. Write all scenes sequentially into a single complete chapter draft
2. Save the entire draft to chXX-draft.md
3. Tell the author the draft is ready for their editing

Rules during drafting:

• First-person, past tense, Phelan's voice (dry wit, ADD tangents, precise observations)
• KDP formatting from first draft (em dashes —, smart quotes, * * * scene breaks)
• Flag continuity concerns: [CONTINUITY FLAG: note]
• Target 3,000–5,000 words total
• End with resolved beat or micro-hook
• All time references (bells, days, day-of-week) must match timeline-book{BOOK}.md

Repetition discipline (pre-empts manuscript-analysis Phase 1):

• No exact phrase (3+ words) twice within a chapter unless it's a deliberate callback or dialogue beat. If you reach for the same phrase twice, vary the second.
• No distinctive word (specific adjective, adverb, non-topical noun) used 4+ times within a chapter. Topical terms (bracelet, crystal, Flaw Sight, moss, seam) are exempt when context requires them.
• Crutch constructions to avoid:
  • "X the way Y [verb] X" — e.g., "registered it the way he registered everything" — limit to one per chapter
  • "It was [noun] of someone who [verb]…" anaphoric pairs — use the anchor noun once, then vary
  • "The X was not X. The X was X in the sense that…" paragraph architecture — once per chapter max
  • "I did not X. I did not Y. I did not Z." anaphora — voice-consistent but limit to one cluster per chapter
  • "Not X. Not Y." fragment openers — limit to 2 per chapter
• Voice pattern quota: noise parentheticals, cataloguing sentences, and dialogue-echo beats are Phelan voice — use them deliberately. If any voice pattern appears 3+ times in a chapter, at least one instance should be structurally different or cut.
• Dialogue-beat echoes ("Tonight..." / "Tonight...", "The seam..." / "The seam...") are intentional rhythm. Use with purpose, not as default fallback when you can't generate distinct exchanges.

Continuity pre-check (pre-empts manuscript-analysis Phase 2): Before writing scenes involving these elements, consult:

• Time references (bells, days, elapsed time) → world/timeline-book{BOOK}.md
• Currency, prices, payments → world/economy.md
• Character knowledge state (who knows what, when) → characters/{name}.md
• 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.

Structural variety (pre-empts manuscript-analysis Phase 3 pacing/POV findings):

• Vary paragraph openings across a chapter. Don't open three consecutive paragraphs with "I …" or "The [noun] …" or "[Character] [verbed]…".
• Vary sentence length within scenes. Action scenes earn clipped fragments; investigation scenes earn longer discursive sentences. Avoid uniform-length paragraphs.
• Noise parentheticals: 4–6 for establishing chapters, 3–5 for ongoing. Each must do narrative work (reveal character, advance plot, humor). Don't place two consecutive parentheticals unless the scene demands it (hyperfocus, crash, action spike).

Pre-handoff self-check: Before saving the draft and telling the author it's ready, run this pass:

1. Phrase repetition scan: Look for any 3+ word phrase used twice. Trim or vary the second instance unless it's a deliberate callback or dialogue echo.
2. Noise count: Count parentheticals. Within target range? If over, cut the one doing the least narrative work.
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.

After saving: Tell the author the draft is in chXX-draft.md and to edit it directly. When they're satisfied with their edits, they should re-invoke /chapter-workflow XX for the final review.

Stage 4: Review

The author has edited chXX-draft.md. Now perform a final review focused on:

1. Clarity — are descriptions, actions, and dialog clear and unambiguous?
2. Grammar — correct spelling, punctuation, tense consistency, subject-verb agreement
3. Chapter flow — does the chapter read smoothly from opening to close? Are transitions between scenes natural?
4. Sentence flow — varied sentence length, no awkward constructions, rhythm feels right for each scene type (clipped in action, discursive in investigation, slower in quiet moments)
5. Voice consistency — every paragraph sounds like Phelan
6. Continuity — cross-check against world/story-summary-book{BOOK}.md and world/timeline-book{BOOK}.md for conflicts with established canon
7. KDP formatting — em dashes, smart quotes, scene breaks, structure
8. Repetition & crutch patterns — apply the Stage 3 repetition discipline as review criteria:
   • Exact 3+ word phrase repeats (not deliberate callbacks or dialogue echoes)
   • Distinctive words used 4+ times (non-topical)
   • 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 (4–6 establishing, 3–5 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.

Stage 5: Continuity Update

Update project files with new canon from the chapter:

• world/story-summary-book{BOOK}.md — add chapter summary, update character tracker, plot threads, financial ledger, and world facts
• world/timeline-book{BOOK}.md — add timeline entries for new chapter (bells, days, elapsed time)
• world/magic/exploits-log.md — new exploits
• characters/ — new or changed characters
• world/locations/ — new locations
• world/ — new world facts

Report what was updated.