plan-review

To get structured feedback on an implementation plan, you can run parallel expert reviews that evaluate architectural soundness, completeness, and feasibility, synthesizing findings into actionable categories like mismatches and improvements for decision-makers.

Yes, you can automate architecture, security, and completeness reviews to run in parallel. This orchestration speeds up early-stage plan validation by spawning multiple expert reviewers simultaneously to evaluate the planned implementation.

Parallel plan validation works by loading repository conventions from CLAUDE.md when present. It applies these repo-specific conventions and reviewers during the assessment to ensure the planned implementation aligns with existing project standards.

The best way to organize plan review findings for traceability is to enforce a structured reviewer format using MISMATCHES, IMPROVEMENTS, and ALTERNATIVES. Findings are saved and presented category-by-category before proceeding to the next step.

To locate a plan file for review, the system accepts a work slug, a full path, or auto-discovers the file from the current Git branch, enabling flexible review workflows without requiring manual file path specification.

Yes, plan review works without manual file paths by auto-discovering the plan file from the current branch. This enables flexible review workflows when you have a planned implementation ready for validation.