planning-validator

You validate planning artifacts by cross-checking traceability matrices, semantic accuracy, and contract compliance using an evidence-first, fail-default posture. This ensures every acceptance criterion and dependency is complete and backed by explicit evidence before downstream execution.

Impact analysis for brownfield changes assesses the blast radius of proposed modifications by cross-validating dependency graphs against existing planning artifacts. It identifies potential conflicts and traceability gaps across stories to prevent silent planning errors before proceeding.

Cross-story validation executes coverage checks across multiple stories to detect conflicts, enforce terminology consistency, and verify contract compliance. It defaults every check to NEEDS WORK, requiring explicit evidence to pass and generating structured guidance packages for any failures.

Yes, per-story validation mode checks individual story artifacts for completeness, semantic accuracy, and traceability immediately after story completion. It outputs structured guidance packages with reasoned corrections and context7 documentation fetch instructions for any identified gaps.

No, validation operates with read-only behavior and writes reports exclusively to plan/validation/* directories. It produces guidance packages for re-dispatch on failures but never modifies the original plan artifacts themselves.

The best way to enforce contract compliance is running phase validation immediately after artifact creation, applying evidence-backed checks that default to FAIL. This prevents drift by verifying consistency, completeness, and terminology enforcement across all planning phases before downstream agents proceed.