Individual skill

document-review

Structural and accuracy review of documents: gaps, clarity, completeness, organization, and claims checked against the code. Use when a brainstorm, plan, spec, ADR, or any doc needs polish before the next workflow step. For exploring new ideas from scratch, use brainstorming instead.

skills/document-review/SKILL.md

Read pinned source

Source commit aee700a03a860d412ddb58c9b9fe57213c9e21dc

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 45
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-coding-assistant Repository topic
ai-tools Repository topic
claude-code Repository topic
skills Repository topic
operations Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 9,778 bytes
SPEC.mddoc · 4,604 bytes
references/reader-test.mddoc · 1,567 bytes

Read excerpt


# Document Review

Improve brainstorm or plan documents through structured review.

## Working rules

- Assess before editing, preserve implementation-relevant constraints and rationale, and distinguish minor edits from substantive decisions.
- A review-only request authorizes findings, not file edits. Apply changes only when the user has requested editing or approved the proposed changes; do not ask again for changes already authorized.

## Step 1: Get the Document

**If a document path is provided:** Read it, then proceed to Step 2.

**If no document is specified:** Ask which document to review (via `AskUserQuestion` in Claude Code, `request_user_input` in Codex, or numbered options in chat as the fallback), or look for the most recent brainstorm/plan in `docs/brainstorms/` or `docs/plans/`.