plan-review

A plan review evaluates implementation plans against established quality standards to surface gaps before execution. It enforces pre-validated structure, requires explicit citations for architectural decisions, and ensures actionable tasks with clear edge-case handling.

The best way to ensure traceable architectural decisions is to enforce explicit citations and rationale within the plan documentation. This validates that every architectural choice has traceable references, producing an audit-ready assessment with severity levels and actionable recommendations.

Auditing a completed plan for quality assurance requires validating its documentation against established criteria. You load the prepared plan document and evaluate its structure, measurable goals, and edge-case handling to generate a formal assessment with severity levels and concrete recommendations.

Yes, plan validation is applicable during plan creation, auditing completed plans, and validating documentation. It enforces pre-validated plan structure via plan_save, requires measurable goals, and ensures actionable tasks are defined with clear edge-case handling to reduce miscommunication.

Automated plan structure validation requires a pre-validated plan structure via plan_save and depends on explicit citations and measurable goals in the documentation. It cannot evaluate undocumented architectural decisions and produces formal assessments limited to the content explicitly present in the plan.