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

2. 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)

3. 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)

4. 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.

5. 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)