proposal-reviewer

A proposal review audits your final plan against actual code to catch missed root causes and hidden regressions. It performs a fresh, independent critique of the problem statement and implementation steps to verify correctness before you proceed with development.

You validate testing coverage by pointing an independent critique process at your proposals directory or final-plan.md path. It verifies the implementation steps, testing coverage, and documentation against the actual codebase to produce actionable guidance and a final review document.

Yes, proposal review works by pointing directly at a specific file path like final-plan.md. You do not need a complex proposals directory structure; the skill performs an independent critique against the codebase as long as the final plan document is accessible.

The best way to find incorrect root-cause assumptions is to run an independent critique of the final plan against the actual codebase. This validates root-cause accuracy and identifies missing steps or hidden regressions before you proceed with implementation.

You should not use an independent plan critique if you lack a finalized final-plan.md or comparable proposals directory. The skill requires a completed plan to audit for root-cause accuracy, implementation steps, and testing coverage against the actual codebase.