doc-review

# Doc-review: multi-persona content-shape review of plans and specs `doc-review` evaluates a requirements doc, plan, spec, or PRD through specialist reviewer lenses. It classifies the document by content shape, selects the lenses the document actually warrants, dispatches them in parallel as read-only subagents, synthesizes their confidence-anchored findings through a multi-stage pipeline, and routes each survivor into one of four handling tiers. The structural invariant: **it never edits the document under review.** The only surface it may write is a single review-record file, and only when persistence is requested. ## Auto-invoke <auto_invoke> <trigger_phrases> - "review this plan" - "review this spec" - "review this PRD" - "review these requirements" - "critique this design doc" </trigger_phrases> Fire automatically on a trigger phrase against a prose document, or on `/doc-review`. Auto-firing is permission to **evaluate**, not permission to fabricate. Every finding still has to clear the evidence-quote and confidence-anchor floor below. A clean "nothing above the floor" is a valid, correct result. <manual_override>`/doc-review [path]` reviews the named document, or lists candidates to choose from when no path is given. `--record` persists a review-record file and stages only it. `mode:headless` makes the run non-interactive (return structured findings, no questions, no record unless `--record`).</manual_override> </auto_invoke> ## When to Apply / NOT Apply when the u...