What problem does it solve? Turning a founder's document review feedback into an actual next version of the document is slow and error-prone: sections get drafted without order, reviewers grade their own work, and the only reviewed copy gets overwritten. This Skill converts a doc epic's backlog into the next iteration of the document with enforced structure. ## Core Features & Use Cases - Wave-based execution: Derives execution waves from the live blocked-by DAG in Linear, with founder-only jam tickets as wave 0, and a resumable execution-order instance file beside the doc. - Draft, fresh-eyes review, revise loop: Each ticket is drafted, then reviewed by a separate context that loads only the gate rubric, ticket, and section, with a 3-loop cap before flagging. - Two-tier gate rubric: Mechanical checks (grep-level) run first, then judgment checks from a calibrated reviewer persona, with verdicts posted as ticket comments. - Snapshot and lock discipline: Snapshots the doc into a dated iterations folder before drafting, and reserves the final integrate-and-lock ticket for founder sign-off. - Use Case: A strategy document with a 23-ticket Linear epic gets its next version built section by section, each section passing an adversarial quality gate before integration, ending with a founder review handoff. ## Quick Start Ask the agent to run the doc iteration loop on the strategy doc's Linear epic and build the next iteration wave by wave.