design-doc-full-pass

Use a full-pass workflow that partitions the document on heading boundaries and dispatches one read-only agent per section. Each agent returns exact old_string to new_string edits with a rationale and risk tier, which a coordinator then applies under whole-doc structural checks.

Use design-doc-full-pass only when the doc is large or heavily reviewed enough that parallel section agents justify their coordination cost. For a single section, one paragraph, or a quick tighten, defer to the plain design-doc skill, which owns the underlying editorial rules.

The coordinator builds a cross-reference map of headings, anchors, intra-doc links, table mirrors, and review-comment anchors before dispatching agents. Every edit is applied as an exact string replacement verified unique across the whole file, and any edit that would alter structure is rejected.

Yes. Where the platform is reachable, it pulls review threads to map which passages reviewers have pinned. When threads cannot be fetched, it conservatively flags any passage a reviewer may have anchored to instead of auto-cutting it.

Edits that touch rationale are discarded outright, since rationale is the most protected content. Framing-only edits are flagged for the author's decision, and only clean redundancies that pass cross-reference checks are auto-applied.

Section agents are read-only and blind to the rest of the doc, so the coordinator must own all cross-reference integrity. Fan-out is capped at 20 concurrent agents, and Workflow-tier orchestration requires explicit user opt-in plus a runbook author.