consistency-check

Name: consistency-check
Availability: InStock
Author: petrsimonidesxart

Detect and report inconsistencies across Epics, Stories, Plans, and PRDs.

Updated Mar 8, 2026

Search Tags:#consistency #validation #compliance #reporting #governance #traceability #artefacts

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill consistency-check-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/consistency-check
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill consistency-check-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Artefact misalignment and governance gaps across Epics, Stories, Plans, and PRDs can lead to inconsistent decision-making and miscommunication. This Skill detects and reports these inconsistencies without modifying artefacts.

Core Features & Use Cases

Cross-artefact linkage verification to ensure traceability from Story to Epic to PRD.
Validation of required fields and inter-artefact consistency (scope, acceptance criteria, and rules).
Governance guardrails and reporting to surface issues with severity and suggested follow-ups.
Use Case: After a planning session, run the check to surface misalignments before implementation.

Quick Start

Run the consistency check after story generation or plan preparation to surface artefact misalignments and generate a report.

Frequently Asked Questions about consistency-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check for inconsistencies across Epics, Stories, and PRDs?▼

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.

Can I use this consistency check to validate scope alignment without altering my planning 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.

When do I need to run a consistency validation on my project artefacts?▼

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.

What is the best way to surface misalignments between stories and plans before implementation?▼

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.

Why does my consistency validation fail during governance gating?▼

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.