review-plan

Reviewing a dev plan against acceptance criteria involves verifying task decomposition, tracking dependencies, and estimating effort by comparing the dev-plan against setup.yaml. This produces structured review artifacts and a decision summary to validate design alignment.

A development task plan review is a structured evaluation of task decomposition, dependencies, and TDD approach to ensure robust development. You need one when you must verify that your dev-plan accurately aligns with design documents and setup.yaml acceptance criteria before implementation.

To verify design alignment and track dependencies, apply design-document and dev-design inputs to cross-reference the dev-plan. This process validates that task dependencies are accurate and effort estimates are realistic, outputting actionable recommendations to update the design-document.

Yes, you can evaluate the TDD approach for an existing dev-plan by applying the design-document and dev-design inputs. The review systematically assesses testing strategies and coverage against setup.yaml acceptance criteria to output a peer-review report under docs/{target_repo}/review-plan/.

Automated dev plan reviews rely heavily on the completeness of setup.yaml acceptance criteria and existing dev-design artifacts. If the input design documents lack detail or the task decomposition is fundamentally flawed, the review cannot generate actionable recommendations to update the design-document effectively.