review-doc

The parent orchestrates. It does not scan unless the host cannot spawn subagents — then it runs one worker at a time. Each check in Checks is one worker.

Work one page at a time. checks/ and logs/ are relative to this skill; docs/ is relative to the project root (docs.json at the root). Publisher-facing usage is in README.md.

Gotchas

• Do not invent pages, procedure steps, prerequisites, audience, or information architecture.
• Do not convert between equivalent docs.page forms (<Info> ↔ GitHub alerts; ![alt](src) ↔ <Image>; <Property> ↔ a short markdown table; <Tabs> / <TabItem> naming).
• Do not apply a fix that would make the page worse.
• Do not auto-apply a held heading rewrite: an edit that changes a ## / ### / # line (any check, not only headings) to wording that slugifies to a different id. Slugify: lowercase, strip non-alphanumerics, spaces to hyphens (Set up iOS → set-up-ios; duplicates get -1, -2). Sentence case or a trailing period that keep the same id may apply. Leave the heading and decision: null; the publisher accepts it and renames the heading and the /page#slug links together.
• If the live page already shows steps, callouts, tabs, cards, or images, re-fetch raw MDX — missing tags in converted HTML are not findings.

Loop