audit

Validates research or plan against hallucination, overscoping, and traceability. Produces a clear PASS/WARN/FAIL verdict.

Best use case

audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Validates research or plan against hallucination, overscoping, and traceability. Produces a clear PASS/WARN/FAIL verdict.

Teams using 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

$curl -o ~/.claude/skills/audit/SKILL.md --create-dirs "https://raw.githubusercontent.com/ferdiangunawan/rpi-stack/main/audit/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/audit/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How audit Compares

Feature / AgentauditStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Validates research or plan against hallucination, overscoping, and traceability. Produces a clear PASS/WARN/FAIL verdict.

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 Skill

Quality gate that validates a research document or plan before the next phase begins.

---

## Agent Compatibility

- OUTPUT_DIR: `.claude/output` for Claude Code, `.codex/output` for Codex CLI.
- If an assumption needs user confirmation, ask directly — don't auto-fail.

## Audit Types

- `/audit research` — Validates research output before planning.
- `/audit plan` — Validates plan output before implementation.

---

## How to Run an Audit

### 1. Load Context

```
Required:
├── Artifact to audit (research-{feature}.md or plan-{feature}.md)
├── Original requirements (Jira description, PRD, or original prompt)
└── AGENTS.md (project conventions)
```

### 2. Run the Three Checks

For each check: list findings, then give a verdict.

---

## Check 1: Hallucination — Is anything invented?

Hallucination = a claim, requirement, or decision that is **not traceable** to the original requirements and is **not a reasonable technical necessity**.

### How to Check

For each requirement, decision, or task in the artifact:
- Can it be traced to the PRD / Jira / prompt? → **Traceable**
- Is it a reasonable inference from context or technical necessity? → **Justified**
- Is it invented with no basis? → **Hallucination**

**Important:** If something looks like an assumption, **ask the user first** before marking it as a hallucination. If the user confirms it → "User-confirmed assumption" (not a hallucination).

### Verdicts

| Finding | Verdict |
|---------|---------|
| No hallucinations found | ✅ PASS |
| Minor assumptions (user-confirmed or clearly justified) | ⚠️ WARN |
| Invented requirements with no basis | ❌ FAIL |

---

## Check 2: Scope Balance — Is it the right amount of work?

Overengineering = adding things not required (abstractions, configs, future-proofing).
Underengineering = missing requirements, missing error handling, missing edge cases.

### How to Check

**Overengineering signals:**
- Abstractions or layers that serve no current requirement
- Configuration options not asked for
- "Future-proofing" without specification
- New patterns when existing patterns suffice

**Underengineering signals:**
- PRD requirements with no corresponding task or coverage
- Happy-path-only implementation (missing error/empty/loading states)
- Missing input validation or auth checks
- Acceptance criteria with no task addressing them

### Verdicts

| Finding | Verdict |
|---------|---------|
| Nothing extraneous, nothing missing | ✅ PASS |
| Minor scope issues that don't block | ⚠️ WARN |
| Significant scope creep or requirement gaps | ❌ FAIL |

---

## Check 3: Traceability — Does every requirement have coverage?

Build a simple matrix: each requirement → covered by task(s) or explained why not.

| Requirement | Covered by | Status |
|-------------|------------|--------|
| R1: {desc} | T1, T3 | ✅ Full |
| R2: {desc} | T2 | ✅ Full |
| R3: {desc} | — | ❌ Missing |

### Verdicts

| Finding | Verdict |
|---------|---------|
| All requirements covered | ✅ PASS |
| Some partial coverage with clear reason | ⚠️ WARN |
| Requirements with no coverage | ❌ FAIL |

---

## Overall Verdict

| Result | Meaning | Action |
|--------|---------|--------|
| **PASS** | All checks green or warn-level | Proceed to next phase |
| **WARN** | Minor issues noted, nothing blocking | Proceed with caution; note items for review |
| **FAIL** | At least one check failed | Stop; fix issues; re-audit |

---

## Output Template

Save to `OUTPUT_DIR/audit-{type}-{feature}.md`:

```markdown
# Audit Report: {Feature} ({Research / Plan})

## Check 1: Hallucination
**Verdict: {PASS / WARN / FAIL}**

Findings:
- {item}: {Traceable / Justified / Hallucination — reason}

{If hallucination: List what must be removed or confirmed}

---

## Check 2: Scope Balance
**Verdict: {PASS / WARN / FAIL}**

Overengineering findings:
- {item or "None"}

Underengineering findings:
- {item or "None"}

{Recommended additions or removals}

---

## Check 3: Traceability

| Requirement | Covered by | Status |
|-------------|------------|--------|
| R1: {desc} | {tasks} | ✅ / ⚠️ / ❌ |

**Verdict: {PASS / WARN / FAIL}**

---

## Pattern Compliance (Plan Audit Only)

| Pattern | Status | Notes |
|---------|--------|-------|
| {pattern from AGENTS.md} | ✅ / ❌ | {notes} |

---

## Overall: {PASS / WARN / FAIL}

### Blocking Issues (must fix before proceeding)
{List or "None"}

### Non-Blocking Issues (noted for awareness)
{List or "None"}

### Next Steps
1. {action}
```

---

## Quick Commands

```
/audit research  — Audit the research output
/audit plan      — Audit the plan output
```

Related Skills

rpi

6
from ferdiangunawan/rpi-stack

Use when implementing features from Jira tickets, PRDs, or user requirements. Orchestrates Research-Plan-Implement workflow with quality gates.

research

6
from ferdiangunawan/rpi-stack

Use when needing to understand requirements before implementation. Gathers context from Jira, Confluence, codebase, and docs. Produces research document with confidence assessment.

plan

6
from ferdiangunawan/rpi-stack

Creates detailed implementation plan from validated research. Produces task breakdown with dependencies and file inventory.

implement

6
from ferdiangunawan/rpi-stack

Executes implementation plan with quality checks and progress tracking. Follows AGENTS.md patterns strictly.

code-review

6
from ferdiangunawan/rpi-stack

Reviews code for correctness, security, performance, and pattern compliance. P0/P1/P2 severity. Absorbs security and performance audit checks.

RPI Stack Skill Distribution

6
from ferdiangunawan/rpi-stack

Lean Research-Plan-Implement workflow skills for Claude Code and Codex.

workspace-surface-audit

144923
from affaan-m/everything-claude-code

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.

DevelopmentClaude

click-path-audit

144923
from affaan-m/everything-claude-code

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.

DevelopmentClaude

local-legal-seo-audit

31392
from sickn33/antigravity-awesome-skills

Audit and improve local SEO for law firms, attorneys, forensic experts and legal/professional services sites with local presence, focusing on GBP, directories, E-E-A-T and practice/location pages.

laravel-security-audit

31392
from sickn33/antigravity-awesome-skills

Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.

SecurityClaude

fda-medtech-compliance-auditor

31392
from sickn33/antigravity-awesome-skills

Expert AI auditor for Medical Device (SaMD) compliance, IEC 62304, and 21 CFR Part 820. Reviews DHFs, technical files, and software validation.

Regulatory ComplianceClaude

fda-food-safety-auditor

31392
from sickn33/antigravity-awesome-skills

Expert AI auditor for FDA Food Safety (FSMA), HACCP, and PCQI compliance. Reviews food facility records and preventive controls.

Regulatory ComplianceClaude