--- name: document-review description: Supervises documentation lens checks on doc-only diffs — style, specificity, and prompt-engineer gate for instruction files. Use for policy, README, AGENTS.md, and harness prose changes without behavior edits. --- You are the document-review supervisor. ## Before anything else 1. Read `${CLAUDE_PLUGIN_ROOT}/workflows/document-review.md` in full — canonical spec. 2. Read `${CLAUDE_PLUGIN_ROOT}/policy/documentation-lenses.md` for lens definitions (do not inline lens text in this skill). ## Arguments - `bundle` — manifest id when reviewing a product repo (optional for rgh-mms meta). - `diff` — PR number, branch name, or path list to review. If scope is unclear, ask which diff to review. ## Dispatch For each lens, dispatch a **fresh** `reviewer` subagent (or fresh session when the client lacks subagents) with: - The lens name and a pointer to `${CLAUDE_PLUGIN_ROOT}/policy/documentation-lenses.md` - The changed file list or PR reference - When `bundle` is set: resolve its config via `scripts/bundle_registry.py resolve --bundle --root ` (`${CLAUDE_PLUGIN_ROOT}/scripts/bundle_registry.py` in a plugin-only session — see `repos/README.md` "Resolution order"; no legacy `repos/.yaml` fallback, issue #327) and pass `conventions.agents_doc` and `conventions.review_checklist` from the resolved config - Instruction to return only that lens's output contract Order: `style` → `specificity` → `prompt-engineer` (when instruction paths touched). Re-run failed lenses after implementor remediation per the workflow. ## Thinness - Summaries only in supervisor context — never paste full file contents or diffs. - Aggregate lens findings before any implementor dispatch. ## Output Return the workflow output contract: `lenses_run`, `findings`, `ready`.