Documentation Review
Own general repository-document quality in an explicit audit-only or authorized edit mode.
Workflow
- Confirm audience, document set, desired outcome, and whether the task authorizes edits.
- Route current-change drift to
docs-drift-review, docs/context/ structure to repo-context-document, semantic contracts to spec-update, journeys to critical-journey-document, and persuasive claims to marketing-claims-review.
- Verify content against implementation, commands, configuration, examples, tests, metadata, and canonical documents.
- Classify evidence-backed findings as
keep, update, merge, split, move, archive, or remove.
- In audit-only mode, return prioritized findings without edits.
- In edit mode, change only the confirmed document set and preserve repository structure and voice unless that structure is the requested defect.
- Use
text-improve on changed prose without changing verified facts, required terminology, or intentional voice.
- Require explicit authority before archiving, removing, or materially expanding the document set.
Do not invent features, commands, architecture, benchmarks, screenshots, promises, or roadmap items; impose a generic template; or broaden a focused request.
Finish with an evidence-backed audit or verified scoped edits, plus unresolved facts needing an owner.
1---2name: docs-review3description: Audit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.4---56# Documentation Review78Own general repository-document quality in an explicit audit-only or authorized edit mode.910## Workflow11121. Confirm audience, document set, desired outcome, and whether the task authorizes edits.132. Route current-change drift to `docs-drift-review`, `docs/context/` structure to `repo-context-document`, semantic contracts to `spec-update`, journeys to `critical-journey-document`, and persuasive claims to `marketing-claims-review`.143. Verify content against implementation, commands, configuration, examples, tests, metadata, and canonical documents.154. Classify evidence-backed findings as `keep`, `update`, `merge`, `split`, `move`, `archive`, or `remove`.165. In audit-only mode, return prioritized findings without edits.176. In edit mode, change only the confirmed document set and preserve repository structure and voice unless that structure is the requested defect.187. Use `text-improve` on changed prose without changing verified facts, required terminology, or intentional voice.198. Require explicit authority before archiving, removing, or materially expanding the document set.2021Do not invent features, commands, architecture, benchmarks, screenshots, promises, or roadmap items; impose a generic template; or broaden a focused request.2223Finish with an evidence-backed audit or verified scoped edits, plus unresolved facts needing an owner.
yarlson