consensus-disagreement-analysis

Compare validator evidence and emit per-criterion consensus resolution reports.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/krzemienski/validationforge --skill consensus-disagreement-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consensus-disagreement-analysis
Source: https://github.com/krzemienski/validationforge/tree/main/skills/consensus-disagreement-analysis
Command: npx skills add https://github.com/krzemienski/validationforge --skill consensus-disagreement-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When multiple validators produce conflicting PASS/FAIL votes for the same journey, teams need a reproducible, evidence-first arbitration process to decide which verdict to trust and whether a re-run or human escalation is required. This Skill provides a disciplined protocol to identify diverging criteria, read and summarize each side's captured evidence, and produce a defensible resolution without modifying validator artifacts.

Core Features & Use Cases

  • Divergence Identification: Scans per-criterion tabulation to locate exactly which criteria caused the journey-level disagreement.
  • Evidence Inventory & Read-Only Analysis: Loads and summarizes each validator's cited evidence, flags missing or zero-byte files, and preserves validator independence by never modifying validator directories.
  • Comparative Sequential Analysis: Invokes sequential-analysis with FAIL as the symptom and PASS evidence as the hypothesis seed, running a four-phase investigation and producing a root-cause style report.
  • Resolution Emission: Produces one of three exhaustive resolutions (MINORITY_CORRECT, MAJORITY_CORRECT, UNRESOLVABLE) and writes ordered artifacts under e2e-evidence/consensus/disagreement-analysis/ for downstream synthesis or human escalation.
  • Use Case: Resolve a split where two validators report FAIL and one reports PASS for a session-persistence criterion by comparing timestamps, screenshots, and network captures and then emitting a criterion-level resolution.

Quick Start

Run consensus-disagreement-analysis on the target journey to compare validator evidence and produce a per-criterion resolution report.

Frequently Asked Questions about consensus-disagreement-analysis

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

FAQPage Schema
How do I resolve conflicting PASS and FAIL votes from multiple e2e validators?

Resolve validator consensus disagreements by comparing captured evidence and adjudicating diverging per-criterion votes to produce a reproducible arbitration decision.

What is the best way to arbitrate end-to-end test disagreements using captured evidence?

Arbitrate end-to-end test disagreements by running a comparative sequential analysis that treats FAIL as the symptom and PASS evidence as the hypothesis seed to identify root causes.

Does consensus arbitration modify the original validator evidence directories?

Consensus arbitration operates read-only on validator evidence directories, preserving validator independence by never modifying artifacts while analyzing missing or zero-byte files.

What resolution outcomes are emitted when arbitrating diverging validator votes?

Arbitration emits one of three exhaustive resolutions—MINORITY_CORRECT, MAJORITY_CORRECT, or UNRESOLVABLE—and writes ordered artifacts to e2e-evidence/consensus/disagreement-analysis/ for human escalation.

When should I use a consensus disagreement analysis for e2e validation?

Use consensus disagreement analysis when multiple validators produce conflicting PASS/FAIL votes for the same journey and a coordinator requires a reproducible, evidence-first arbitration decision.