Sprint 56f: Human-readable file naming - Chapter_N_draft/review_a/b/c/final
This commit is contained in:
57
steps/romance_chapter_pass1_draft.yml
Normal file
57
steps/romance_chapter_pass1_draft.yml
Normal file
@@ -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.
|
||||
Reference in New Issue
Block a user