Check Structure

---
name: check-structure
description: The between-sections pass — coherence, the seams between parts, the skim layer (the title chain alone tells the story), structural repetition, and set-level continuity across a multi-piece deliverable. Returns findings and suggested edits; the writer folds them in. Never mutates the draft. TRIGGER when checking a draft's flow, section order, title chain, or how a sequence holds together. DO NOT TRIGGER for a single sentence's words (edit-sentences), genericness (check-ai-writing), or claim backing (check-claims).
---

# Check the structure

One Process: read the piece as an argument moving in one direction, not a stack of blocks. This pass owns the seams between sections, the skim layer (the title chain alone tells the story), and repetition across parts. It never touches the words inside a single sentence; that is edit-sentences. Whether the ARGUMENT's order is the right selling order is check-strategy's; this pass owns whether the joins between sections, in whatever order they sit, actually hold. A missing claim or unbacked promise is check-claims, flagged here, never papered over with a smoother transition.

This pass returns findings and suggested edits and never mutates the draft — beside the writer in production and inside a review round alike, it writes findings in review-copy's finding format and edits nothing. The writer folds the accepted fixes, including a smoothed seam, into the next numbered draft. Where the fix would add an argument, a claim, or a proof point, name it for the writer — that is a writer's job.

## 1. Walk the title chain

### Read the titles alone, top to bottom, and demand the whole story
The skim layer must carry the argument on its own: the promise arrives, what's-in-it-for-me lands early, a problem title is resolved by a later title, and the mechanical checks hold (pronouns resolve, each title stands alone, opener variety, no broken deixis).
Never: a title chain that only makes sense once the bodies are read.

## 2. Walk the seams

### Make every section's first line a sane next thought after the prior close
A reader crosses a break carrying momentum; the seam keeps it or spends it. A good join closes the prior beat, opens a question the next beat answers, and holds the through-line. Bridge each structure on its own terms: agitation inherits the exact problem just named; the lesson falls out of the story's specific ending; the proof backs the exact benefit just promised.
Example: a section titled to introduce the product followed by a body opening on the product's backstory — a jump no reader makes. Name every broken bridge.
Never: bridge with filler ("furthermore", "that being said", "but here's the thing") — a connective adverb is the absence of a transition; if it is the only bridge available, reorder or cut a section.

## 3. Sweep coherence, budgets, and repetition

### Hold the ownership map and spend no fact or shape twice
Against Brief.md's angle and objection inventories and the draft's own section order (Wireframe.md once the writer has produced it): each section owns its point, no fact is spent in two sections, and no two sections close on the same clause shape. Watch house slop — any phrase recurring across sections or drafts is forming a tell.

### Check that no two questions share an underlying question
No two questions on a page share an underlying question.
Example: "Can I bring in work I already have?" and "Can I take my work out later?" both ask whether work moves freely in and out.
Never: list both as separate questions when answering one answers the other.

IF the deliverable is a set (a sequence, a campaign, several pieces):
## 4. Sweep set-level continuity

### Read the set as one argument
Continuity of promises across pieces, one argument across the sequence, and no cross-piece verbatim reuse. Five clean pieces cannot hide a blocked sequence — the set is its own reviewable unit.

Verification: the title chain read alone and judged whole; every seam named passed or bridged; the budget and repetition sweep run against Brief.md's and Wireframe.md's inventories; for a set, continuity checked across all pieces.