Sprint 56f: Human-readable file naming - Chapter_N_draft/review_a/b/c/final

steps/blog_draft_step.yml

@@ -0,0 +1,36 @@
+type: think
+max_tokens: 4000
+hint: |
+  BLOG POST DRAFT
+
+  ASSIGNMENT
+  Title: {item_title}
+  Brief: {item_brief}
+  Target reader: {audience}
+  Voice: {voice}
+  Word count target: {item_target_words} words
+  Keywords to work in naturally: {item_keywords}
+
+  Before writing, confirm:
+    - TOPIC and TARGET READER
+    - HOOK: the first sentence drops the reader into a real scenario or provocative question
+    - PROMISE: the one thing they walk away with
+    - KEY POINTS to cover (use the brief above)
+    - TONE and WORD COUNT TARGET
+    - CALL TO ACTION
+
+  Write the full blog post:
+    - # Title as H1 (make it specific and curiosity-driven, not generic)
+    - Optional subhead in italics
+    - Opening hook: first 2–3 sentences pull the reader in immediately
+    - Body: 3–5 sections with bold subheadings, short readable paragraphs
+    - At least one concrete example, number, or real scenario per section
+    - "Try This Week" or equivalent action section before the closing
+    - Memorable closing line that reinforces the promise
+
+  Tone rules (apply the voice above):
+    - Peer-to-peer. Write like a knowledgeable friend, not a corporate brochure.
+    - Use "you" and "your" — not "one" or "the reader."
+    - Short sentences preferred. No filler paragraphs.
+    - No listicles of 10+ items without grouping them into themes.
+    - Work the keywords in naturally — never stuff them.

steps/blog_polish_step.yml

@@ -0,0 +1,20 @@
+type: think
+max_tokens: 4000
+model: power
+hint: |
+  BLOG POST POLISH
+
+  Read your draft as the target reader would on their phone.
+
+  Apply these editorial passes in sequence:
+    1. CUT — eliminate any warmup sentences, vague generalities, or brochure-speak
+    2. SHARPEN — every subheading should be scannable and specific
+    3. HOOK CHECK — does the opening pull in the first two sentences?
+    4. CTA CHECK — is the call to action specific and doable this week?
+    5. VOICE CHECK — does it sound human and direct throughout?
+    6. KEYWORD CHECK — are the keywords present and naturally integrated (not stuffed)?
+
+  Target word count: stay within the specified range. Quality over quantity.
+
+  Output ONLY the polished final blog post starting with # [Title].
+  No commentary, no "Pass 2" label, no preamble.

steps/chapter_pass0_bible.yml

@@ -0,0 +1,60 @@
+type: think
+hint: |
+  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
+
+  GENRE GUIDE: Your skills section contains exactly the guide for {genre_name}. Apply it fully.
+
+  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.
+    - Never pull facts from a deliverable whose filename indicates a later chapter than {chapter_ref}.
+
+  ⚠️ CRITICAL: Your task name tells you EXACTLY which chapter to write.
+  Look at the CURRENT MESSAGE — write THAT chapter and ONLY that chapter.
+  Do NOT write Chapter 1 unless the message explicitly says "Chapter 1".
+
+  STEP 1 — READ THE OUTLINE / CHARACTER BIBLE:
+    Look at PROJECT DELIVERABLES for the outline file (it contains the Character Bible
+    if this is a fiction project, and the Chapter Outline for all projects).
+    Extract and record:
+      - Protagonist: exact name, voice description, age (if fiction)
+      - Love interest and supporting characters: exact names and roles (if fiction)
+      - World rules / constraints (if paranormal or speculative)
+      - This chapter's summary, emotional beat, and closing hook from the outline
+    If no outline/bible is available, use the character names and project details
+    from the task description above — be CONSISTENT throughout the book.
+
+  STEP 2 — FIND THE PREVIOUS CHAPTER:
+    Look at PROJECT DELIVERABLES for the chapter that comes BEFORE this one.
+    If no previous chapter exists (this IS Chapter 1), skip to STEP 4.
+
+  STEP 3 — QUOTE THE ENDING:
+    Copy the LAST 2–3 sentences of the previous chapter here, word for word.
+    Label them: "PREVIOUS CHAPTER ENDED WITH: ..."
+    Your new chapter MUST pick up from this exact moment.
+
+  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
+      - EMOTIONAL ARC: What does the protagonist feel at start vs end?
+      - CHAPTER GOAL: What plot event MUST happen here?
+      - KEY BEATS: 3–5 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
+
+  STEP 5 — PREVIOUS CHAPTER CHARACTER STATE (if available):
+    If context contains a block starting with "PREVIOUS CHAPTER CHARACTER STATE:",
+    include it verbatim in the prompt under the heading:
+      "CHARACTER CONTINUITY: The previous chapter ended with these character states:
+       {prev_character_state}"
+    These states override any outline prediction that conflicts with them — the character
+    is ALREADY in this emotional/physical state at the start of this chapter.
+    If no character state was provided, skip this block entirely.
+
+  Stop here. Output ONLY the draft prompt. Do NOT write chapter prose yet.

steps/chapter_selfcheck.yml

@@ -0,0 +1,63 @@
+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.
+    6. OPENING HOOK: Check the PASS 0 draft prompt ({steps[0].text}) for a line labeled
+       "LOCKED PREVIOUS CHAPTER HOOK:". If present, verify the chapter's opening paragraph
+       directly resolves it. If not, add a brief resolution sentence at the opening —
+       do not leave a locked hook unanswered.
+    7. AUTHOR'S INTENT: Check the PASS 0 draft prompt ({steps[0].text}) for a line
+       starting with "AUTHOR'S INTENT:". If present, confirm the completed chapter
+       satisfies that intent — note whether it was honored or partially missed.
+
+  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 FORMAT:
+    Start your response with a VALIDATION LOG section:
+      VALIDATION LOG:
+      1. BEAT & HOOK: [check pass/fail with brief note]
+      2. NAMES & POV: [check pass/fail with brief note]
+      3. CONTINUITY TERMS: [check pass/fail with brief note]
+      4. FORMATTING: [check pass/fail — note any fixes applied]
+      5. WORD FLOOR: [check pass/fail — include word count]
+      6. OPENING HOOK: [check pass/fail or N/A]
+      7. AUTHOR'S INTENT: [honored / partially missed — note / N/A if no intent set]
+
+    Then output the separator on its own line:
+      ---BEGIN CHAPTER---
+
+    Then output the final chapter text (corrected where structurally required,
+    verbatim everywhere else). Start the chapter directly with the chapter title
+    and first line. No preamble or commentary within the chapter text.

steps/cozy_chapter_pass1_draft.yml

@@ -0,0 +1,62 @@
+type: think
+model: power
+hint: |
+  PASS 1 — WRITE THE COZY MYSTERY CHAPTER DRAFT
+
+  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
+    - If the draft prompt contains a line starting with "LOCKED PREVIOUS CHAPTER HOOK:",
+      your FIRST LINE MUST directly resolve that hook — the reader expects the answer immediately
+    - If the draft prompt contains a line starting with "AUTHOR'S INTENT:", treat it as a
+      binding creative directive — your draft must satisfy that intent in full
+    - Follow the KEY BEATS in order, but write with full scene depth — don't skip
+    - All character names, the town layout, and recurring elements must be consistent with the bible/outline
+    - Every dialogue exchange must be tight and voice-distinct
+    - Show, don't tell — externalize emotion through action, detail, and dialogue
+    - Every scene beat moves the story forward OR reveals character (no filler)
+    - End with the CLOSING HOOK you planned
+    - Match the prose style guide: {prose_style}
+    - Target length: {chapter_target_words} words — write the FULL chapter, not a summary
+    - ⚠️ DO NOT stop early. If you have not reached {chapter_target_words} words, continue
+      writing — add warm detail, community scenes, extended dialogue beats, and character moments
+      until you hit the target. Short chapters will be REJECTED in adjudication.
+
+  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.
+
+  COZY MYSTERY CRAFT RULES — these apply on every page:
+    - THE SETTING IS A CHARACTER: The small town, the bakery, the knitting circle — these are
+      not backdrop, they are the emotional heart of the series. Give the setting sensory life on
+      every page: smells, textures, seasonal details, the rhythms of community life.
+    - COZY WARMTH IS NON-NEGOTIABLE: There is death, but no graphic gore. Danger is present, but
+      the world is ultimately safe and resolvable. Readers come here for comfort. The protagonist
+      is competent, good-hearted, and embedded in a community that matters to them.
+    - CLUE INTEGRITY: Every clue dropped must be discoverable by the reader in retrospect.
+      No solutions pulled from nowhere. Suspects and red herrings are played fair — they have
+      real motives, even if they didn't commit the crime.
+    - THE AMATEUR SLEUTH VOICE: Your protagonist is not a professional detective. They notice
+      things because they KNOW this community, these people, these routines. The edge they have
+      over police is intimacy, not technique. Honor that — let their community knowledge be their
+      superpower.
+    - ENSEMBLE IS EVERYTHING: Cozy mysteries live or die on the recurring cast. Every chapter
+      should feel the community around the protagonist: the best friend who over-shares, the
+      rival who isn't entirely wrong, the authority figure who is simultaneously helpful and
+      obstructive. These relationships are the true product.
+    - HUMOR AND HEART: Cozy mysteries are warm books. There must be humor — light, character-
+      driven, never mean-spirited. There must be heart — the protagonist cares about these people
+      and this place, even the irritating ones.
+    - PACING: Cozy chapters move through scenes naturally, never rushed. A chapter might include
+      an investigation beat, a community scene, and a personal moment. Balance all three.
+
+  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.

steps/fiction_editorial_spawn.yml

@@ -0,0 +1,62 @@
+type: package
+hint: |
+  The draft chapter has been written, self-checked, and committed.
+
+  CRITICAL — include 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 chapter.
+
+  Now spawn the three independent editorial reviewers
+  and the roundtable debate. Use the exact task_names shown — the roundtable depends_on all three.
+schema:
+  chapter_text: string
+spawn:
+  - task_type: chapter_review
+    task_name: "Review (Devon): {chapter_ref}"
+    agent_name: Devon
+    priority: 6
+    context:
+      chapter_text: "{chapter_text}"
+      review_focus: developmental
+      genre_name: "{genre_name}"
+      genre_audience: "{genre_audience}"
+      chapter_ref: "{chapter_ref}"
+  - task_type: chapter_review
+    task_name: "Review (Lane): {chapter_ref}"
+    agent_name: Lane
+    priority: 6
+    context:
+      chapter_text: "{chapter_text}"
+      review_focus: line
+      genre_name: "{genre_name}"
+      genre_audience: "{genre_audience}"
+      chapter_ref: "{chapter_ref}"
+  - task_type: chapter_review
+    task_name: "Review (Cora): {chapter_ref}"
+    agent_name: Cora
+    priority: 6
+    context:
+      chapter_text: "{chapter_text}"
+      review_focus: continuity
+      genre_name: "{genre_name}"
+      genre_audience: "{genre_audience}"
+      chapter_ref: "{chapter_ref}"
+  - task_type: chapter_roundtable
+    task_name: "Roundtable: {chapter_ref}"
+    agents:
+      - Devon
+      - Lane
+      - Cora
+    priority: 7
+    context:
+      chapter_text: "{chapter_text}"
+      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}"
+      - "Review (Cora): {chapter_ref}"

steps/romance_chapter_pass1_draft.yml

@@ -0,0 +1,57 @@
+type: think
+model: power
+hint: |
+  PASS 1 — WRITE THE ROMANCE CHAPTER DRAFT
+
+  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
+    - If the draft prompt contains a line starting with "LOCKED PREVIOUS CHAPTER HOOK:",
+      your FIRST LINE MUST directly resolve that hook — the reader expects the answer immediately
+    - If the draft prompt contains a line starting with "AUTHOR'S INTENT:", treat it as a
+      binding creative directive — your draft must satisfy that intent in full
+    - Follow the KEY BEATS in order, but write with full scene depth — don't skip
+    - All character names must be consistent with the bible/outline
+    - Every dialogue exchange must be tight and voice-distinct
+    - Show, don't tell — externalize emotion through action, detail, and dialogue
+    - Every scene beat moves the story forward OR reveals character (no filler)
+    - End with the CLOSING HOOK you planned
+    - Match the prose style guide: {prose_style}
+    - Target length: {chapter_target_words} words — write the FULL chapter, not a summary
+    - ⚠️ DO NOT stop early. If you have not reached {chapter_target_words} words, continue
+      writing — add interiority, sensory detail, extended dialogue beats, and scene transitions
+      until you hit the target. Short chapters will be REJECTED in adjudication.
+
+  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.
+
+  ROMANCE-SPECIFIC CRAFT RULES — these apply on every page:
+    - TENSION IS THE PRODUCT: Every scene between leads must have an undercurrent of want,
+      resistance, or denial. The reader must feel the pull even in mundane exchanges.
+    - THE SLOW BURN BANK: Each chapter should deposit into the romantic tension account.
+      A lingering glance. An interrupted touch. A sentence that almost says something.
+      No withdrawal (resolution) until the story earns it.
+    - INTERNAL STAKES: Romantic conflict is internal as much as external. What is she afraid
+      of? What is she protecting herself from? Give us the emotional wound and let it shape
+      every interaction with the love interest.
+    - SEXUAL TENSION (if appropriate to heat level): Not explicit in narrative unless the
+      project specifies — but physical awareness is always there. The smell of his jacket.
+      The accidental brush of hands. The protagonist is hyper-aware of proximity.
+    - SWOON MOMENTS: Plan at least one moment per chapter that the reader will screenshot
+      and send to a friend. One line, one gesture, one micro-scene that is memorable.
+    - DIALOGUE IS SUBTEXT: Romance characters rarely say what they mean. Give us the conversation
+      underneath the conversation. She says "It's fine." She means "I need you to fight for this."
+    - PACING: Slow build. Do NOT resolve the primary romantic tension early. Push through to
+      the black moment before the earned resolution.
+
+  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.

steps/scifi_chapter_pass1_draft.yml

@@ -0,0 +1,60 @@
+type: think
+model: power
+hint: |
+  PASS 1 — WRITE THE SCIENCE FICTION CHAPTER DRAFT
+
+  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
+    - If the draft prompt contains a line starting with "LOCKED PREVIOUS CHAPTER HOOK:",
+      your FIRST LINE MUST directly resolve that hook — the reader expects the answer immediately
+    - If the draft prompt contains a line starting with "AUTHOR'S INTENT:", treat it as a
+      binding creative directive — your draft must satisfy that intent in full
+    - Follow the KEY BEATS in order, but write with full scene depth — don't skip
+    - All character names, alien species, and world terminology must be consistent with the bible/outline
+    - Every dialogue exchange must be tight and voice-distinct
+    - Show, don't tell — externalize emotion through action, detail, and dialogue
+    - Every scene beat moves the story forward OR reveals character (no filler)
+    - End with the CLOSING HOOK you planned
+    - Match the prose style guide: {prose_style}
+    - Target length: {chapter_target_words} words — write the FULL chapter, not a summary
+    - ⚠️ DO NOT stop early. If you have not reached {chapter_target_words} words, continue
+      writing — add interiority, sensory detail, extended dialogue beats, and scene transitions
+      until you hit the target. Short chapters will be REJECTED in adjudication.
+
+  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.
+
+  SCIENCE FICTION CRAFT RULES — these apply on every page:
+    - WORLDBUILDING BY IMMERSION: Do not pause to explain your world. Characters live in it.
+      Let technology, politics, and history emerge through action and dialogue, not exposition.
+      "She scanned for temporal residue" tells us about the world without stopping to define it.
+    - INTERNAL LOGIC IS NON-NEGOTIABLE: Your world's rules must be established and honored.
+      If FTL travel has a cost, that cost appears on every jump. If psionics tire the user,
+      fatigue is present. Consistency is the contract with the reader.
+    - THE IDEA IS A CHARACTER: Science fiction ideas (the alien biology, the AI ethics
+      dilemma, the political paradox) are as much a character as any person. Give the idea
+      presence in every chapter — don't let it fade into backdrop.
+    - SCALE WITHOUT LOSING THE HUMAN: The universe can be vast, the stakes cosmic — but anchor
+      each chapter in one person's experience, one pair of hands, one heartbeat. The reader
+      cannot feel interstellar scale; they CAN feel one soldier's fear before the breach.
+    - SENSE OF WONDER: Every chapter should have at least one moment that enlarges the reader's
+      imagination — a view, a revelation, a technology, a moral question — that makes the
+      universe feel genuinely strange and genuinely real at the same time.
+    - ALIEN AUTHENTICITY: Non-human characters must not be humans in costumes. Alien cognition,
+      alien values, alien humor. If a species has a different relationship with time or memory,
+      show it in their dialogue and choices.
+    - PACING: Alternate tension with revelation. Each chapter should push the external plot
+      forward AND deliver one new piece of world or character understanding.
+
+  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.

steps/ya_chapter_pass1_draft.yml

@@ -0,0 +1,53 @@
+type: think
+model: power
+hint: |
+  PASS 1 — WRITE THE YA CHAPTER DRAFT
+
+  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
+    - If the draft prompt contains a line starting with "LOCKED PREVIOUS CHAPTER HOOK:",
+      your FIRST LINE MUST directly resolve that hook — the reader expects the answer immediately
+    - If the draft prompt contains a line starting with "AUTHOR'S INTENT:", treat it as a
+      binding creative directive — your draft must satisfy that intent in full
+    - Follow the KEY BEATS in order, but write with full scene depth — don't skip
+    - All character names must be consistent with the bible/outline
+    - Every dialogue exchange must be tight and voice-distinct
+    - Show, don't tell — externalize emotion through action, detail, and dialogue
+    - Every scene beat moves the story forward OR reveals character (no filler)
+    - End with the CLOSING HOOK you planned
+    - Match the prose style guide: {prose_style}
+    - Target length: {chapter_target_words} words — write the FULL chapter, not a summary
+    - ⚠️ DO NOT stop early. If you have not reached {chapter_target_words} words, continue
+      writing — add interiority, sensory detail, extended dialogue beats, and scene transitions
+      until you hit the target. Short chapters will be REJECTED in adjudication.
+
+  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.
+
+  YA-SPECIFIC CRAFT RULES — these apply on every page:
+    - AUTHENTIC TEEN VOICE: Your protagonist thinks and speaks like an actual teenager.
+      Not a precocious adult, not a caricature. Short, fragmented thoughts. Reactions before
+      analysis. The world feels high-stakes even for "small" problems — that's real teen experience.
+    - EMOTIONAL STAKES: Everything feels life-or-death. A rumor is social death. Being left out
+      is gut-punch lonely. A first kiss is epoch-defining. Honor this even if the plot is bigger.
+    - NO ADULT WISDOM INJECTION: Your teen protagonist does not land on wise, balanced conclusions.
+      They overcorrect, lash out, apologize awkwardly, misread situations. Growth is messy.
+    - INTERIORITY IS CORE: In YA, the internal monologue IS the story. External event + internal
+      reaction × 3 = a chapter. Give us at least two beats of deep interiority per scene.
+    - FRIENDSHIP/BELONGING: Even if the plot is about monsters, the emotional core is about
+      whether the protagonist belongs, is loved, is seen. Keep that alive in every chapter.
+    - PACING: YA chapters end on hooks. Momentum over description. No scene lasts longer than
+      it earns. Get out of scenes early.
+
+  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.