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/.

Step 2: Assess

Read through the document and ask: