scene-writing

keberle's avatarfrom keberle

Draft or edit fiction scenes with continuity discipline, strong scene structure (hook → turn → button), and anti-invention rules. Use for "write scene", "draft chapter", "edit scene", and prose-writing requests.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 27, 2025
[Drafting]

When & Why to Use This Skill

The Scene Writing skill is a professional-grade tool for fiction authors and narrative designers, engineered to draft and edit high-quality prose with rigorous continuity discipline. By implementing a structured 'Hook → Turn → Button' framework and strict anti-invention rules, it ensures that every scene remains faithful to established canon, character backgrounds, and specific POV constraints, significantly reducing narrative inconsistencies in long-form storytelling.

Use Cases

  • Drafting new fiction chapters: Generate cohesive prose that automatically integrates existing character files, timelines, and world-building elements from your project database.
  • Structural scene refinement: Transform loose drafts into compelling narrative units by enforcing a professional scene structure (Hook, Turn, and Button).
  • Maintaining narrative continuity: Validate scene beats against established 'canon' to prevent biographical errors, brand hallucinations, or timeline contradictions.
  • POV and Style Discipline: Execute prose writing that strictly adheres to a single POV anchor and specific tonal guidelines (e.g., tense, voice, and formatting) defined in style guides.
namescene-writing
descriptionDraft or edit fiction scenes with continuity discipline, strong scene structure (hook → turn → button), and anti-invention rules. Use for "write scene", "draft chapter", "edit scene", and prose-writing requests.

Scene Writing

Write or edit scenes while respecting canon, POV discipline, and continuity.

Pre-Writing Checklist (MANDATORY)

Before writing prose:

  1. Load constraints
  • .github/copilot-instructions.md
  • elements/checklist.md
  • elements/pov.md, elements/tone.md
  • voice/style.md, voice/format.md
  1. Load canon needed for THIS scene
  • elements/timeline.md (if present)
  • elements/characters.md (if present)
  • Individual character files for everyone on-page (elements/characters/<name>.md)
  • Relevant setting/event canon (elements/setting.md, elements/events/*.md if used)
  1. Load continuity context
  • The relevant outline for this episode/chapter (elements/outlines/...)
  • Prior scenes that directly connect (same episode/chapter, or latest appearance of key characters)
  1. Verify beat mechanisms (CRITICAL) For each planned beat:
  • HOW does it happen?
  • WHO knows what, and how did they learn it?
  • WHEN does it happen relative to adjacent scenes? If unclear: flag [NEEDS CLARIFICATION: ...] instead of inventing.
  1. Boundary enforcement If working from an outline, define:
  • What must happen in THIS scene
  • What belongs to the NEXT scene Stop at the scene’s button.

During Writing

Non-Negotiables

  • Follow the chosen POV and tense (elements/pov.md).
  • One POV anchor per scene (unless your POV rules allow otherwise).
  • Don’t invent high-specificity details (brands, precise biographical facts, makes/models, addresses) unless canon.

Opening Discipline

  • Don’t open by recapping the last scene.
  • Prefer starting mid-action or mid-conversation.

Scene Structure

  • Hook → Turn → Button

After Writing

  • If new facts were introduced, update the appropriate elements/** canon.
  • If using elements/timeline.md, add/update the timeline entry for the scene.

Bundled References

  • references/mcdonald-rule.md — in-medias-res opening discipline
  • references/king-principles.md — broadly useful craft heuristics (trait-based)