pipeline

Runs an autonomous build, six-lens review, and adjudication pipeline from an approved plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions often produce plausible code, review their own work, and report success without independent verification. This Skill enforces a delivery discipline where intent is written down first, code is reviewed by six independent lenses in fresh context, and a judge adjudicates findings — with a single human approval gate as the only checkpoint. ## Core Features & Use Cases - Autonomous end-to-end delivery: Takes an approved plan and runs build, six parallel review lenses, adjudication, and a recheck of the judge's own commits without further supervision. - Single approval gate: The user approves the plan once; the pipeline records that authorization in state.json and never asks again, while detecting stale approvals from runs that died before building. - Append-only review rounds: Re-runs on a branch add new review files without deleting earlier ones, and escalations can be covered afterward by reviewing only the delta since the last verdict. - Use Case: After writing and approving a plan for a feature branch, run the pipeline once before opening a pull request so the diff is built, reviewed from six independent angles, adjudicated, and reported in verdict.md. ## Quick Start Ask the AI to run the quorum pipeline for the current branch's approved plan and report the verdict when it finishes.

Frequently Asked Questions about pipeline

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

FAQPage Schema
How do I run an autonomous AI code review pipeline on a branch?▼

Write and approve a plan first, then invoke the pipeline with the branch slug. It builds the change, runs six independent review lenses in parallel, adjudicates findings, and writes verdict.md without further human involvement.

How do I re-run an AI review after more commits land on a branch?▼

Re-running on the same branch is supported: reviews are append-only, so a second run writes new review files alongside the first round. The approval gate triggers again because every unattended run needs its own authorization.

Can I run this pipeline in CI or from a git hook?▼

No. The pipeline must never be wired into CI, hooks, or automatic triggers because the judge writes code, and unattended commits without an approval gate break the safety model. CI should run the regression suite instead.

What happens if the pipeline run dies before building anything?▼

The approval is treated as stale: state.json is reset to the planned stage and plan.md status reverts, re-arming the gate. The failure is reported and the run is not relaunched on the spent authorization.

How do I review code written after the pipeline escalated a decision?▼

Run the pipeline with skipBuild and a diff range from verdict.head in state.json to HEAD. This reviews only the uncovered delta with a new review round instead of re-paying for a full branch run.

What are the limitations of the six-lens AI review panel?▼

All lenses are Claude models, so the panel reduces but does not eliminate correlated blind spots; a genuinely independent panel would span providers. The judge also gets at most two passes to reach a green test suite before stopping.