audit

Detects architecture-specification drift in codebases with ADRs and OpenSpec.

30|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill audit-joestump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/audit
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill audit-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and prioritizes mismatches between architecture decisions, specifications, and implementation to prevent unnoticed drift, reduce technical debt, and guide remediation.

Core Features & Use Cases

  • Full-project or scoped audits: Scan ADRs, OpenSpec specs, and source code to surface Code vs Spec, Code vs ADR, ADR vs Spec inconsistencies, coverage gaps, stale artifacts, and policy violations.
  • Severity-aware findings and remediation: Classify issues as CRITICAL/WARNING/INFO using RFC 2119 mappings and produce ordered recommended actions and acceptance criteria.
  • Team review and scrum triage: Support single-agent audits, reviewer teams (--review), or a multi-agent scrum triage ceremony (--scrum) with prioritized themes and optional issue creation in the project's tracker.

Quick Start

Run a full audit by invoking /design:audit on your project or /design:audit security to scope the analysis to security-related artifacts.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I detect architecture-specification drift in my codebase?

Architecture-specification drift is detected by scanning source files against ADRs and OpenSpec specs to surface Code vs Spec, Code vs ADR, and ADR vs Spec inconsistencies, coverage gaps, and policy violations.

How do I scope a code audit to target security, APIs, or database domains?

Code audits can scope analysis to security, APIs, or database domains by targeting specific artifacts. Scoped audits extract relevant ADR and spec files, then scan source files to surface inconsistencies within the targeted domain.

How are audit findings classified and prioritized for remediation?

Audit findings are classified as CRITICAL, WARNING, or INFO using RFC 2119 mappings. This severity-aware classification produces ordered recommended actions and acceptance criteria to guide technical debt remediation.

Can I run a scrum triage ceremony for architecture audit findings?

Architecture audit findings support a multi-agent scrum triage ceremony with prioritized themes. This mode enables team review, artifact pairing, and optional issue creation directly in a project's tracker.

Do I need ADRs and OpenSpec specs to perform a full-project audit?

Full-project audits are applicable to codebases with ADRs and OpenSpec specs. These design artifacts are extracted and paired with source files to detect mismatches, reduce technical debt, and guide remediation.

What is the best way to identify stale artifacts and coverage gaps in software architecture?

Identifying stale artifacts and coverage gaps requires scanning ADRs, OpenSpec specs, and source code. The audit surfaces inconsistencies, stale artifacts, and policy violations to prevent unnoticed drift and reduce technical debt.