doc-iteration-loop

Builds the next iteration of a founder document from a Linear epic backlog using wave-ordered drafting and adversarial review gates.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill doc-iteration-loop-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-iteration-loop
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/doc-iteration-loop
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill doc-iteration-loop-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about doc-iteration-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a document review backlog into the next version of the doc?▼

Run the doc iteration loop against the doc's Linear epic. It derives execution waves from the blocked-by DAG, snapshots the current doc, then drafts, reviews, and revises each section ticket until it passes the gate rubric.

How does the fresh-eyes review gate work for document sections?▼

A separate context that did not draft the section loads only the gate rubric, the ticket, and the drafted section. It runs mechanical checks first, then judgment checks, and returns a PASS or REVISE verdict with findings.

What prerequisites does the doc iteration loop need before running?▼

It needs a Linear epic whose tickets each cover one section with acceptance criteria and a quality metric, an honest blocked-by DAG, jam tickets for open founder decisions, and a render the founder can review.

What happens when a section keeps failing the quality gate?▼

Revision is capped at three loops. If the section still fails, the ticket is marked flagged for the founder, the open findings are commented on the ticket, and the loop moves on without softening the rubric.

Does the doc iteration loop overwrite the reviewed document?▼

No. Before any drafting it snapshots the current doc into a dated iterations folder beside it, preserving the exact state the founder reviewed. The final integrate-and-lock ticket is always the founder's manual sign-off.