quorum:verify

Run all done-criteria checks and generate a pass/fail verification report.

15|4|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/berrzebb/consensus-loop --skill quorum-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quorum:verify
Source: https://github.com/berrzebb/consensus-loop/tree/main/skills/verify-implementation
Command: npx skills add https://github.com/berrzebb/consensus-loop --skill quorum-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

After implementing code, teams need a repeatable verification step to ensure all done-criteria are satisfied before submitting to quorum audit. This skill runs all defined checks and provides a clear pass/fail result that helps prevent unverified changes from advancing.

Core Features & Use Cases

  • Runs all done-criteria checks across CQ, T, CC, CL, S, I, FV, CV and outputs a unified report.
  • Supports both interactive and headless modes; headless exits with a non-zero status on failures and interactive mode presents guided feedback.
  • Enables evidence readiness by validating changes before audit submission.

Quick Start

Run the verification to generate a pass/fail report and prep evidence for audit.

Frequently Asked Questions about quorum:verify

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

FAQPage Schema
How do I automate done-criteria checks for code changes before an audit?

Automate done-criteria checks by running all defined verification categories and generating a standardized pass/fail report. This validates code changes and ensures evidence readiness before submitting to a quorum audit.

Can I run verification checks in a headless CI pipeline?

Yes, verification checks support headless modes for automated CI pipelines. Headless execution runs all checks and signals status with a non-zero exit code on failures to halt pipeline progression.

What done-criteria categories are covered during the verification process?

The verification process covers CQ, T, CC, CL, S, I, FV, and CV done-criteria categories. It orchestrates all these checks and outputs a unified report detailing the pass or fail status of each.

Does the verification report provide interactive feedback for local implementation?

Yes, the verification tool supports interactive mode for local code implementation. This mode presents guided feedback on done-criteria failures, helping developers resolve issues before pre-audit submission.

What is the best way to prevent unverified code changes from advancing in a pipeline?

The best way to prevent unverified changes from advancing is to automate done-criteria checks in headless mode. This generates a pass/fail report and returns a non-zero exit code on failure to block pipeline progression.