factory-coherence-validation

What problem does it solve?

Standard SDLC pipeline gates only validate artifact status and iteration freshness, but miss silent semantic misalignments between interdependent deliverables. These gaps lead to broken downstream work, rework, and undetected scope drift when agents consume incoherent upstream artifacts.

Core Features & Use Cases

• Scope-Based Traceability Checks: Runs configurable check sets tailored to BLUEPRINT, IMPLEMENT, and QA agent workflow stages to validate only relevant artifact pairs.
• Cross-Artifact Gap Detection: Catches critical misalignments like missing component coverage for Gherkin scenarios, mismatched data schemas between user journeys and design docs, orphaned test cases, and unresolved upstream contract dependencies.
• Increment and Slice Plan Validation: Ensures incremental slicing strategies have well-formed increment plans and slice maps, with mandatory RDR compliance for capability-value slicing.
• Use Case: When a BLUEPRINT agent runs the --approve command for a new feature, CVP validates that all spec scenarios map to design components, all user journey data fields exist in the data model, and all contract endpoints have corresponding test cases before marking the feature as approved.

Quick Start

Use the factory-coherence-validation skill to run a full cross-artifact coherence check for feature ID FEAT-456 before the QA agent runs its final verification gate.