consistency-check-protocol

Verifies sub-agent output against a decision anchor and emits pass, warn, or fail verdicts.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/soli92/soli-projects --skill consistency-check-protocol-soli92
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: consistency-check-protocol
Source: https://github.com/soli92/soli-projects/tree/main/.cursor/skills/consistency-check-protocol
Command: npx skills add https://github.com/soli92/soli-projects --skill consistency-check-protocol-soli92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sub-agents in multi-agent pipelines can silently contradict earlier architectural decisions, and without an independent check these contradictions propagate downstream undetected. This Skill provides a 5-step protocol for an external consistency-checker agent to detect such contradictions before they cause damage. ## Core Features & Use Cases - Anchor integrity validation: Verifies the SHA-256 checksum of the decision_anchor before any comparison, aborting with an [anchor-tampered-pre-check] error on mismatch. - Contradiction detection with severity grading: Compares each anchored decision against the output artifact and classifies findings as critical, major, or minor with a confidence score. - Deterministic verdict matrix: Computes pass/warn/fail verdicts from findings and confidence thresholds, with degraded mode when the token budget (default 5000) is exceeded. - Fail-closed escalation: Fail verdicts log an EP-013 consistency_decision event, write an ERROR to wiki/log.md, and escalate to a human gate without auto-rollback. - Use Case: After a dev-agent generates an implementation plan, the consistency-checker agent runs this protocol to confirm the plan does not contradict the locked stack and security decisions recorded in the decision anchor. ## Quick Start Ask the consistency-checker agent to run the consistency check protocol on the sub-agent output artifact against the current decision anchor and report the verdict with any findings.

Frequently Asked Questions about consistency-check-protocol

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

FAQPage Schema
How do I check if an AI agent's output contradicts previous decisions?▼

Run the consistency check protocol: read the decision anchor, extract technical decisions from the output artifact, then compare each anchored decision against the output for explicit or implicit contradictions. Each contradiction is logged as a finding with severity and confidence.

What is a decision anchor in multi-agent workflows?▼

A decision anchor is a structured YAML record of locked architectural decisions with a SHA-256 checksum over its canonical JSON. It acts as the contract that sub-agent outputs are verified against, and any checksum mismatch aborts the check with an anchor-tampered error.

Can a sub-agent run the consistency check on its own output?▼

No. The protocol enforces rule R.Q1bis: only the independent consistency-checker agent may invoke it, never the sub-agent that produced the output. This separation mirrors the evaluator-optimizer pattern where the reviewer is external to the generation loop.

What happens when the consistency check verdict is fail?▼

A fail verdict triggers fail-closed behavior: an EP-013 consistency_decision event is logged, an ERROR is written to wiki/log.md, and the case escalates to a human gate with the findings. No automatic rollback is performed in the current version.

What happens if the consistency check exceeds its token budget?▼

The checker enters degraded mode when output extraction exceeds the configured token budget (default 5000 tokens per invocation). It returns a warn verdict tagged [checker-budget-exceeded] and flags the artifact for manual review.