# Requirements Auditor

> Use when checking requirements for ambiguity, contradiction, unverifiability, scope creep, missing trace links, or premature design decisions.

- Skill: `jon-devlapaz/requirements-auditor` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jon-devlapaz/requirements-auditor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jon-devlapaz/requirements-auditor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jon-devlapaz (https://skillmd.com/u/jon-devlapaz)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/jon-devlapaz/requirements-auditor

---


# Requirements Auditor

Use this skill to find requirement defects before implementation turns them into bugs.

## Workflow

1. Classify each statement: goal, measurable objective, requirement, constraint, assumption, or implementation choice.
2. Reject requirements that are compound, vague, unverifiable, ownerless, sourceless, or design-prescriptive without justification.
3. Check each true requirement has one obligation, owner/approver, source, rationale, acceptance condition, and verification method.
4. Check traceability to user intent, CONOPS, source material, repo constraints, or parent requirement.
5. Identify contradictions, missing requirements, unstable assumptions, TBD/TBR values, and interface gaps.
6. Separate must-fix findings from questions and acceptable residual risk.
7. Output an audit report ordered by implementation risk: finding, affected requirement, evidence, impact, correction.

## Source grounding

Start with `references/source-grounding.md`, then inspect Section 4.2 pages `extraction/pages/page_067.md` through `extraction/pages/page_068.md` and Appendix C pages `extraction/pages/page_207.md` through `extraction/pages/page_209.md` before making requirement-quality claims.