- Home
- Skills
- Agents & Orchestration
- Quorum: plan, build, review, adjudicate for Claude Code
Quorum: plan, build, review, adjudicate for Claude Code
Plan, build, multi-lens review, and adjudication - run step by step or autonomously from an approved plan, ending in a pull request.
$15.99
Works with the AI Agents you already use
Quorum: plan, build, review, adjudicate for Claude Code
Example session with this skill installed
/quorum:1-plan "Add a JWT-based authentication middleware to the Express API. It should check the Authorization header and attach the user object to the request."
- Read your context and instructions
- Compiled the quorum
I have investigated the request and prepared a work plan. I created the branch feat/jwt-auth-middleware and initialized the work directory.
Work Plan: feat/jwt-auth-middleware
| Field | Value |
|---|---|
| Slug | feat/jwt-auth-middleware |
| Status | planned |
| Author | claude-code |
Intent
Implement a robust JWT authentication middleware for the Express application to protect downstream routes and provide user context.
Acceptance Criteria
- Middleware extracts Bearer token from
Authorizationheader. - Returns
401 Unauthorizedif token is missing or malformed. - Returns
403 Forbiddenif JWT verification fails (expired/invalid). - Decoded payload is attached to
req.user. - Integration tests verify successful auth and all failure modes.
Proposed Design
graph TD
A[Incoming Request] --> B{Has Header?}
B -- No --> C[Return 401]
B -- Yes --> D{Verify JWT}
D -- Invalid --> E[Return 403]
D -- Valid --> F[Attach user to req]
F --> G[Next Middleware]
Next steps
- Review the plan above and the generated
docs/work/feat/jwt-auth-middleware/plan.md. - Approve the plan by running
/quorum:2-build feat/jwt-auth-middleware. - The build step will start implementing the middleware once you confirm.
Connects securely to your tools. The creator never sees your data.
About this skill
Development velocity often craters during the review and adjudication phase, where code intent gets lost in translation. Quorum is a complete pipeline for Claude Code that enforces a rigorous plan-build-review-adjudicate workflow to ensure production code matches user intent. It eliminates the "LGTM" culture by running every change through six independent, specialized review lenses—behavior, correctness, security, and more—before a final adjudication step resolves findings.
What it does
- Structured Planning turns requests into testable intent, acceptance criteria, and Mermaid diagrams before a single line of code is written.
- Autonomous Implementation builds features step-by-step from approved plans, tracking progress to maintain state across sessions.
- Multi-Lens Review spawns independent subagents to audit code through six specific remits, including behavioral testing and security.
- Automated Adjudication acts as a judge to verify review findings, apply accepted fixes, and generate a final verdict.
- Regression Guarding installs CI gates and mechanical checks to ensure requirements, tests, and review records remain untampered.
How it works
- Plan Use
/quorum:1-planto investigate the request and lock down acceptance criteria indocs/work/<slug>/plan.md. - Review Execute
/quorum:3-reviewto generate independent review files for the built change. - Adjudicate Run
/quorum:4-quorumto process review findings and finalize the code. - Monitor Use
/quorum:statusor/quorum:historyto track the state of work items across the repository.
Frameworks & tools
The pipeline uses Claude Code plugins, Python helpers, and shell scripts. It integrates with Git for branch management and supports standard CI/CD environments like GitHub Actions and GitLab CI.
Why this beats prompting it yourself
Standard prompts often suffer from self-confirmation bias, where the agent assumes its own code is correct. Quorum forces independence by spawning subagents with fresh context and specific audit remits, ensuring defects are caught before they reach a human reviewer.
Use cases
- Complex Refactoring managing multi-file changes where intent must be strictly preserved.
- Security-Sensitive Features requiring an independent security lens audit before merging.
- Long-Running Tasks needing persistent state and progress tracking across multiple Claude sessions.
- CI/CD Hardening automating the generation of behavioral regression tests and merge gates.
Known limitations
The pipeline requires installation as a Claude Code plugin to access ${CLAUDE_PLUGIN_ROOT}. All artifacts are stored locally in the repository under docs/work/.
Open source
Quorum is also available free and open source (MIT) at https://github.com/AiFirstDevelopment/quorum. This listing contains the same code with no exclusive functionality; you are paying for a packaged, ready-to-install copy.
Requires installation as a Claude Code plugin. Artifacts stored in docs/work/. Review lenses require subagent support or sequential execution. Commands are branch-dependent.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 29 days ago
Requires