plan-reviewer

To ensure PR specs have testable acceptance criteria, you need to evaluate implementation plans to verify each criterion is specific, measurable, and linkable to validation steps. This surfaces gaps in feature documentation before development starts.

Documenting integration touchpoints and risks in a feature plan requires identifying data flows and system impacts early. You must explicitly record top risks alongside their mitigations and capture open questions as formal decisions within the plan.

Adding automated test intents and manual validation steps to a project plan involves defining a complete validation strategy. You must document both the manual validation procedures and the intended automated tests to support the acceptance criteria.

Yes, plan review can be applied to software projects across different teams. It automates the evaluation of feature docs and implementation plans to ensure validation planning and acceptance criteria are consistently documented regardless of the team.

Implementation plans fail validation planning checks when manual validation steps or automated test intents are missing. The review process requires explicit documentation of both validation methods to ensure all acceptance criteria are fully supported.

You should not use automated plan review for feature documentation if your project lacks initial acceptance criteria or implementation specs. The review requires existing plan details to evaluate testability, integration touchpoints, and risk mitigations effectively.