storyweaver-chapter-wave git:20260607.e22b11eA

Immutable. This exact content never changes and is served at /api/v1/blob/0b24e2a6f5166772.

---
name: storyweaver-chapter-wave
description: "Draft one or more chapters, scenes, beats, or sections from accepted contracts, then route through continuity, developmental review, critique, and revision."
---

# Storyweaver Chapter Wave

Use this skill when drafting a bounded prose wave from an accepted outline or contract.

## Coordinates

- Primary agent: Scene Writer
- Continuity agent: Continuity Keeper
- Review agent: Developmental Editor
- Pressure review agent: Critique Reviewer, when requested or high-risk
- Revision agent: Revision Weaver

## Required Reading Order

1. Target contract in `chapter-contracts/` or scene contract
2. `story-bible.md`
3. `outline.md` and `beat-map.md`
4. `continuity-ledger.md`
5. `constraints.md`
6. `research/research-pack.md`, if present
7. `protocol-notes.md`, if present
8. `state.md`

## Workflow

1. Select target chapter, scene, beat, or section range.
2. Draft in layers: plot/action, interiority/relationship, dialogue/voice, integrated prose.
3. Write draft under `chapters/` or `scenes/`.
4. Send drafting notes to the continuity keeper.
5. Update `continuity-ledger.md`.
6. Run developmental review.
7. Run critique review when requested, high-risk, source-sensitive, or protocol-sensitive.
8. Route to revision, human pause, or acceptance.
9. Update `state.md`.

## Artefacts Read

- Contracts, bible, outline, continuity, constraints, research, protocol notes

## Artefacts Written

- `chapters/chapter-##.md` or `scenes/scene-##.md`
- `reviews/chapter-##-developmental.md`
- `reviews/chapter-##-critique.md`, when run
- Updated `continuity-ledger.md`
- Updated `revision-log.md`, when revision occurs

## Pause Conditions

- The contract has not been accepted.
- Drafting would violate protocol or source boundaries.
- The draft takes a viable but meaning-changing direction requiring human choice.

## Acceptance Checklist

- [ ] Drafted section fulfills the contract or route explains why not.
- [ ] Continuity ledger is updated.
- [ ] Review route is recorded.
- [ ] Any revision is captured in `revision-log.md`.