원클릭으로
audit
Validates research or plan against hallucination, overscoping, and traceability. Produces a clear PASS/WARN/FAIL verdict.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Validates research or plan against hallucination, overscoping, and traceability. Produces a clear PASS/WARN/FAIL verdict.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Reviews code for correctness, security, performance, and pattern compliance. P0/P1/P2 severity. Absorbs security and performance audit checks.
Executes implementation plan with quality checks and progress tracking. Follows AGENTS.md patterns strictly.
Creates detailed implementation plan from validated research. Produces task breakdown with dependencies and file inventory.
Use when needing to understand requirements before implementation. Gathers context from Jira, Confluence, codebase, and docs. Produces research document with confidence assessment.
Use when implementing features from Jira tickets, PRDs, or user requirements. Orchestrates Research-Plan-Implement workflow with quality gates.
SOC 직업 분류 기준
| name | audit |
| description | Validates research or plan against hallucination, overscoping, and traceability. Produces a clear PASS/WARN/FAIL verdict. |
Quality gate that validates a research document or plan before the next phase begins.
.claude/output for Claude Code, .codex/output for Codex CLI./audit research — Validates research output before planning./audit plan — Validates plan output before implementation.Required:
├── Artifact to audit (research-{feature}.md or plan-{feature}.md)
├── Original requirements (Jira description, PRD, or original prompt)
└── AGENTS.md (project conventions)
For each check: list findings, then give a verdict.
Hallucination = a claim, requirement, or decision that is not traceable to the original requirements and is not a reasonable technical necessity.
For each requirement, decision, or task in the artifact:
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).
| Finding | Verdict |
|---|---|
| No hallucinations found | ✅ PASS |
| Minor assumptions (user-confirmed or clearly justified) | ⚠️ WARN |
| Invented requirements with no basis | ❌ FAIL |
Overengineering = adding things not required (abstractions, configs, future-proofing). Underengineering = missing requirements, missing error handling, missing edge cases.
Overengineering signals:
Underengineering signals:
| Finding | Verdict |
|---|---|
| Nothing extraneous, nothing missing | ✅ PASS |
| Minor scope issues that don't block | ⚠️ WARN |
| Significant scope creep or requirement gaps | ❌ FAIL |
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 |
| Finding | Verdict |
|---|---|
| All requirements covered | ✅ PASS |
| Some partial coverage with clear reason | ⚠️ WARN |
| Requirements with no coverage | ❌ FAIL |
| 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 |
Save to OUTPUT_DIR/audit-{type}-{feature}.md:
# 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}
/audit research — Audit the research output
/audit plan — Audit the plan output