← ClaudeAtlas

doc-reviewlisted

Editorial review of a doc as writing — structure (cuts, reorganization), prose (clarity fixes), and an adversarial pass (gaps, ambiguities, contradictions). Use when the user says "doc review", "tighten this doc", "review the PRD as writing", or "editorial review".
rterakedis/leanwheel-skills · ★ 2 · Code & Development · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Doc Review Skill **Goal:** Review a document as *writing*, not as a plan. `/check-readiness` checks whether the planning docs are aligned and complete; this skill checks whether they are clear, dense, and unambiguous. Planning docs are re-read by the model in every downstream session — cutting a bloated PRD by 30% is a token saving that recurs on every `/create-story`, `/dev-story`, and flywheel run for the life of the project. Three passes, one skill. **CONTENT IS SACROSANCT (Passes A + B):** never change what ideas say — only how they're organized and expressed. Pass C may *question* substance, but it only reports; it never edits meaning. ## Inputs - **target** — file path. If none given, offer: `docs/prd.md`, `docs/architecture.md`, `docs/epics.md`, `docs/project/brief.md`, or "other". - **reader type** — auto-detected, confirm with user: - `llm` for docs consumed by AI sessions (`prd.md`, `architecture.md`, `epics.md`, epic-context files, `CLAUDE.md`): consistent terminology, no hedging, unambiguous antecedents, dependency-first ordering, structured formats over prose. LLM docs may get *longer* where explicitness beats brevity. - `humans` for guides (`docs/setup/`, `docs/maintainer/`, README, guide files): preserve comprehension aids — examples, summaries, expectation- setting, visual breathing room. Don't cut warmth as "fluff". ## Pass A — Structure (always first) 1. State the doc's purpose in one sentence: "This document exists to