4-quorum

Adjudicates code review findings, applies accepted fixes, and writes a verdict file.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/AiFirstDevelopment/quorum --skill 4-quorum-aifirstdevelopment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 4-quorum
Source: https://github.com/AiFirstDevelopment/quorum/tree/main/plugins/quorum/skills/4-quorum
Command: npx skills add https://github.com/AiFirstDevelopment/quorum --skill 4-quorum-aifirstdevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After multiple review lenses produce conflicting findings on a code change, someone must decide which findings are real, fix the valid ones, and produce an auditable verdict — this Skill performs that adjudication step instead of letting the AI that wrote the code grade its own work. ## Core Features & Use Cases - Finding adjudication: Verifies every review finding against the actual code and assigns each one a disposition of Accepted, Rejected, or Escalated with stated reasoning. - Fix application and regression gating: Applies minimal accepted fixes, runs the full test suite, and refuses to report a verdict over a red suite. - Verdict and state recording: Writes a structured verdict.md covering acceptance criteria, dispositions, escalations, and enforcement posture, then records pipeline state via guard and state scripts. - Use Case: After six review lenses flag twelve findings on a pull request, run this step to confirm three are real defects, fix them, reject the rest with reasons, escalate one API design decision to the user, and produce a verdict the reviewer can read instead of re-deriving the reasoning from the diff. ## Quick Start Run the quorum adjudication step for the work item identified by its slug to judge all review findings and produce the verdict.

Frequently Asked Questions about 4-quorum

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

FAQPage Schema
How do I adjudicate conflicting code review findings from multiple reviewers?▼

Verify each finding against the actual code rather than trusting reviewer confidence, then assign one disposition: Accepted (fix it), Rejected (state why), or Escalated (requires a user decision). The verdict file records every disposition with reasoning as an audit trail.

What is the quorum pipeline adjudication step?▼

It is step 4 of the quorum plugin, acting as judge over the plan, the diff, and all review lens outputs. It applies accepted fixes, runs the regression suite until green, and writes verdict.md with an outcome of ready, ready with follow-ups, or blocked.

Can the adjudicator edit the plan's acceptance criteria?▼

No. The adjudicator is measured against the plan's Intent, Acceptance criteria, and Non-goals and may never edit them. It also cannot weaken or delete tests to resolve findings; a genuinely wrong test becomes an Escalated finding instead.

When should a review finding be escalated instead of fixed?▼

Escalate when the plan itself is wrong, two reviews conflict on a genuine design tradeoff, a fix would be destructive or change public API or data, or a proper fix is a larger piece of work. Escalations state what the user must decide with options and a recommendation.

Why does the verdict require a green test suite?▼

A verdict reported over a red suite means the adjudicator's own fixes may have broken something, and the outcome would be untrustworthy. The step explicitly forbids finishing until the full regression suite passes, including fixing breakage caused by its own changes.