audit

Audit specs, plans, code, and content against evidence with YAML verdict artifacts.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill audit-michael-conrad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/audit
Command: npx skills add https://github.com/michael-conrad/.opencode --skill audit-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Audit skill provides a structured approach to verify accuracy, coherence, and fidelity of specs, plans, code, and generated content, ensuring claims are supported by evidence and drift is detected early.

Core Features & Use Cases

  • Self-contained audit workflows: audits are dispatched to clean-room sub-agents via task(subagent_type="general"), shielding the orchestrator from verification work.
  • Verification of spec, plan, code, and guideline integrity across runs, with cross-checks and evidence trails.
  • Artifact-driven verdicts: auditors write YAML verdict artifacts that feed downstream processes like cross-validation and completion.
  • Drift detection and quality controls: supports spec drift, plan fidelity, coherence checks, and content audits to ensure ongoing alignment.

Quick Start

Invoke the audit workflow and dispatch a verification task to a clean-room sub-agent using task(subagent_type="general").

Frequently Asked Questions about audit

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

FAQPage Schema
How do I verify spec fidelity and detect drift in generated content?▼

Spec fidelity verification and drift detection are handled by dispatching clean-room sub-agents to cross-check content against evidence. This process enforces live-tool validation and generates YAML verdict artifacts to ensure claims are fully supported and auditable.

What is a clean-room audit workflow for cross-validation?▼

A clean-room audit workflow isolates verification logic by dispatching tasks to sub-agents, shielding the orchestrator from the verification work. This ensures objective cross-validation of specs, plans, and code with structured evidence trails.

How do I audit generated code and plans against original specifications?▼

Auditing generated code and plans involves dispatching a verification task to a clean-room sub-agent. The sub-agent cross-checks the output against original specs, detects any coherence drift, and writes YAML verdict artifacts for downstream processes.

Can I use sub-agents to shield my orchestrator during guideline audits?▼

Yes, guideline audits are dispatched to clean-room sub-agents via task(subagent_type="general"). This shields the orchestrator from verification work while enforcing live-tool evidence and generating reproducible YAML verdict artifacts.

Why do I need YAML verdict artifacts for content verification?▼

YAML verdict artifacts are required to feed downstream cross-validation and completion processes. They provide a structured, reproducible evidence trail that ensures auditable results when verifying content, specs, or code fidelity.

Does this audit approach work for plan fidelity checks across multiple teams?▼

Yes, the audit workflow supports plan fidelity checks and cross-validation across teams. It enforces live-tool evidence and generates YAML verdict artifacts to ensure ongoing alignment and detect spec drift effectively.