consistency-check

Scan GDDs against the entity registry and report conflicts.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill consistency-check-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/consistency-check
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill consistency-check-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents brittle, conflicting design documentation by scanning all GDDs for mismatches against a central entity registry, so your studio-scale agent system stays coherent as it grows.

Core Features & Use Cases

  • GDD cross-document consistency scanning: Compares registered entity/item/formula/constant values against every in-scope GDD to find contradictory facts.
  • Grep-first performance optimization: Reads the registry once, then uses targeted Grep extraction with limited context to avoid costly full document reads.
  • Conflict triage and actionable reporting: Produces a structured report (conflicts, stale registry entries, unverifiable mentions) and guides resolution before downstream architecture.

Quick Start

Run consistency-check to scan all registered entities across all design/gdd documents for value conflicts and produce a resolution-focused report.

Frequently Asked Questions about consistency-check

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

FAQPage Schema
How do I detect cross-document inconsistencies in GDDs?

Cross-document inconsistencies are detected by scanning GDDs against a central entity registry to compare registered entity, item, formula, and constant values, producing a structured PASS or BLOCKED conflict report.

What is the best way to check entity registry conflicts before architecture creation?

Checking entity registry conflicts before architecture creation involves running a grep-first consistency scan across all GDDs, outputting a structured PASS or BLOCKED conflict report with optional registry correction guidance.

Can I run a consistency check for a single entity or item instead of the full registry?

Yes, you can run scoped consistency checks for a single entity or item. The system supports full, since-last-review, entity, and item modes to perform targeted conflict detection without scanning the entire registry.

How does grep-first conflict detection work for large design documents?

Grep-first conflict detection works by loading the registry once, then performing targeted grep extraction with limited context across design GDDs to avoid costly full document reads, performing deep reads only on identified conflicts.

What types of conflicts are reported during a GDD consistency scan?

A GDD consistency scan reports contradictory facts, stale registry entries, and unverifiable mentions. It outputs a structured PASS or BLOCKED conflict report with optional registry correction guidance to resolve issues before downstream architecture.

When should I run a GDD consistency check in my design workflow?

You should run a GDD consistency check immediately after writing new GDDs and before holistic review or architecture creation. This ensures registered entity values remain coherent across all in-scope design documents as your system grows.