document-review

Structured document review applies active lenses to find gaps and unstated assumptions, scoring the plan against quality criteria. It identifies the single most critical improvement and makes minimal inline edits, gating substantive changes for approval.

Quality scoring evaluates product plans for clarity, completeness, specificity, and YAGNI to determine next-step readiness. The review checks for avoided decisions and scope creep, highlighting exactly what must be fixed before proceeding.

Yes, document review applies targeted checks including Product, Design, Security, Scope guardrails, and Adversarial lenses based on signals found in the document. These active review lenses surface risks and security gaps specific to your ADRs.

Scope guardrails evaluate specs against YAGNI to identify unnecessary content and prevent scope creep. The structured review surfaces avoided decisions and unstated assumptions, scoring specificity to ensure the spec remains tightly bounded.

No, the review avoids premature rewriting by auto-fixing only minor issues and asking approval for substantive changes. It keeps edits inline and minimal, preserving your original brainstorming content while prioritizing structural improvements.

You need a structured document review when preparing brainstorms, plans, specs, or ADRs for the next workflow step. It improves clarity and organization by identifying gaps, avoided decisions, and unstated risks before you commit to development.