plan-review

To validate an implementation plan against coding guidelines, you can run an automated plan review that checks your phases for surface testing compliance, public API exposure, and observability requirements to ensure alignment before implementation begins.

Surface testing compliance in plan review means verifying that your tests target public API usage rather than internal functions, ensuring that test progress aligns correctly with the defined implementation phases of your project.

You can enforce documentation and governance standards in project planning by applying an automated review checklist that validates your plans against CLAUDE.md guidelines, ensuring clear, traceable documentation and proper project governance structure.

Yes, automated plan review validates plan structure by ensuring each phase delivers working, testable increments with a clean separation of concerns, guiding end-to-end plan validation for your implementation roadmap.

The best way to catch misalignments with coding standards before implementation is to run an automated plan guideline review that identifies gaps in surface testing, API exposure, and project governance early in the planning phase.

No specific dependencies are required to run a plan guideline review, as the skill operates independently to analyze your implementation plans and verify compliance with coding standards, testing guidelines, and documentation requirements.