quorum:audit
Run a quorum audit manually — trigger consensus review, re-run failed audits, test audit prompts, or force a specific provider. Use when the hook-based auto-trigger didn't fire, or you want explicit control.
Best use case
quorum:audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run a quorum audit manually — trigger consensus review, re-run failed audits, test audit prompts, or force a specific provider. Use when the hook-based auto-trigger didn't fire, or you want explicit control.
Teams using quorum:audit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/audit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How quorum:audit Compares
| Feature / Agent | quorum:audit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run a quorum audit manually — trigger consensus review, re-run failed audits, test audit prompts, or force a specific provider. Use when the hook-based auto-trigger didn't fire, or you want explicit control.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Audit Manual cross-model review trigger. ## Knowledge Read `agents/knowledge/protocols/audit.md` for the full protocol.
Related Skills
quorum:wb-parser
Parse work-breakdown files into structured requirements tables. Extracts Req IDs, target files, acceptance criteria, dependencies. Triggers on 'parse WB', 'extract requirements', '요구사항 추출', 'WB 파싱'.
quorum:verify
Run all 8 done-criteria checks (CQ/T/CC/CL/S/I/FV/CV) with 20 analysis tools and 5-language registry. Deterministic tools only — zero LLM tokens. Triggers on 'verify', 'self check', 'pre-audit', '검증', '자가 검증'.
quorum:status
Show quorum status — audit state, skill health, or both. Subcommands: audit (gate verdicts, locks, retro), skills (wrapper parity, trigger conflicts), all (everything). Triggers on 'status', 'skill status', 'gate status', '상태'.
quorum:planner
Design tasks into tracks with work breakdowns. Writes and maintains PRDs, generates DRM-driven documents. Use whenever the user mentions planning, PRD, tracks, features, requirements, work breakdown, or 설계/기획.
quorum:orchestrator
Session orchestrator — reads handoff, picks unblocked tasks, distributes to parallel workers, tracks agent assignments, manages correction cycles.
quorum:merge
Squash-merge a worktree branch into target with structured commit message. Use after audit consensus and retrospective.
quorum:harness-bootstrap
Bootstrap a quorum-governed agent team for any project. Analyzes domain, designs team architecture, generates agents and skills with quality gates. Triggers on: 'harness 구성', 'set up harness', 'bootstrap harness', 'build a harness'.
quorum:fde-analyst
Analyze failure scenarios for PRD requirements using Failure Driven Engineering. Generates failure tables with severity classification and derives new WBs. Use after DRM confirmation, before WB drafting. Triggers on 'failure analysis', 'FDE', '실패 분석', '장애 시나리오'.
quorum:designer
Generate and validate design documents (Spec, Blueprint, Domain Model, Architecture) with mandatory mermaid diagrams. Use after PRD confirmation when DRM requires Design Phase. Triggers on 'generate design', 'design docs', '설계 문서', '설계 생성'.
quorum:tools
Run any of the 20 quorum analysis tools — codebase, quality, domain checks, RTM/FVM, and audit history. Use whenever you need code analysis or domain checks.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
click-path-audit
Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.