document-review

Structure a document review by applying a stepwise guided process: retrieve the document, assess it, evaluate against defined criteria, identify improvements, and provide inline updates. This structured review surfaces gaps, ambiguities, and missing assumptions in brainstorm or planning drafts.

The best way to refine a planning document is through criteria-driven evaluation, checking for clarity, completeness, specificity, and YAGNI constraints. This process identifies ambiguities and provides inline change guidance to ensure team alignment before proceeding.

Yes, you can use a structured review process across evolving drafts, from initial brainstorms to formal plans. It specifically surfaces gaps, ambiguities, and missing assumptions by applying consistent evaluation criteria throughout the iterative refinement process.

Evaluate a brainstorm document by applying criteria-driven checks for completeness and specificity. The guided review process assesses the document against these defined standards, identifying areas that lack detail or are missing necessary components.

A limitation of this guided review process is that it requires a defined workflow and specific evaluation criteria upfront. Without these prerequisites, the review cannot effectively generate inline change guidance or actionable next-step prompts for the team.

Yes, iterative document refinement works for team alignment by offering next action prompts and supporting multiple review iterations. This reduces ambiguity and ensures all collaborators are aligned on the finalized plan before execution.