What problem does it solve?
Prevents shallow or schema-breaking intent epic outputs by enforcing the ICE structure, tenet compliance, scenario testability, and provenance traceability before downstream workflow stages proceed.
Core Features & Use Cases
- Validates ICE epic schema contract: Ensures identity and exactly the four required sections appear in the correct order, rejecting any unknown or legacy top-level keys.
- Enforces tenet and content quality heuristics: Applies human-readability checks and guards against jargon-heavy, placeholder, or non-user-observable outcomes.
- Checks scenarios, recovery pairing, and dependency wiring: Verifies success/failure structure and ensures before/after connections, cycles, and mock pairing are consistent across the full epic batch.
- Produces structured, field-level failure reports: Returns a validation result YAML with per-epic, per-field violations for fast regeneration and iteration.
Quick Start
Run validate-intent-epics during the specify stage after generating intent epics to produce a validation result YAML and block the pipeline on any structural or blocking tenet violations.
