consistency-check

To check for inconsistencies across Epics, Stories, and PRDs, run a consistency validation after story generation or planning. This surfaces artefact misalignments, verifies linkage, and generates a detailed report without modifying the original artefacts.

Yes, you can validate scope alignment without altering artefacts because the consistency check operates as a read-only governance guardrail. It enforces frontmatter identity and anti-collision guards before writing a report detailing issues and severity.

You need to run consistency validation after story generation and plan preparation, before implementation begins. Use it during governance gating to verify linkage, completeness, and compliance across Epics, Stories, Plans, and PRDs to prevent inconsistent decision-making.

The best way to surface misalignments between stories and plans is to run a consistency check after planning sessions. This identifies scope and acceptance criteria inconsistencies, providing governance reporting with severity levels and suggested follow-ups.

Consistency validation fails during governance gating when it detects frontmatter identity issues, broken artefact linkage, scope misalignment, or anti-collision guard violations. The generated report will detail these specific issues and their severity for follow-up.