document-review

# Document Review Improve brainstorm or plan documents through structured review. ## 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, or look for the most recent brainstorm/plan in `docs/brainstorms/` or `docs/plans/`. ## Step 2: Assess Read through the document and ask: - What is unclear? - What is unnecessary? - What decision is being avoided? - What assumptions are unstated? - Where could scope accidentally expand? - Is this technically feasible with the current architecture? - Are there security implications in what's proposed? These questions surface issues. Note findings without fixing yet. ## Step 3: Activate Review Lenses Based on the document's content, activate specialized review perspectives. Scan for signals and apply matching lenses: | Lens | Signals | What it checks | |------|---------|----------------| | **Product** | User-facing features, customer language, market claims, scope decisions | Problem framing, value proposition clarity, whether scope matches stated goals | | **Design** | UI/UX references, user flows, wireframes, interaction descriptions | Flow completeness, interaction gaps, accessibility considerations | | **Security** | Auth/authorization, API endpoints, PII, payments, tokens, encryption | Auth model gaps, data exposure risks, missing threat considerations | | **Scope guardian** | Multiple priority tiers (P0/P1/P2), large requir...