# requirements-audit

> Use when you need to validate that a project's requirements set is consistent, versioned, and ambiguity-resistant (REQ/ADR/AC/Index/Changelog), and to produce a deterministic pass/fail report.

- Author: Yifan Gong
- Repository: moplord/everything-claude-code
- Version: 20260202131643
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/moplord/everything-claude-code
- Web: https://mule.run/skillshub/@@moplord/everything-claude-code~requirements-audit:20260202131643

---

---
name: requirements-audit
description: Use when you need to validate that a project's requirements set is consistent, versioned, and ambiguity-resistant (REQ/ADR/AC/Index/Changelog), and to produce a deterministic pass/fail report.
---

# Requirements Audit (Deterministic Gate)

This skill provides a deterministic linter/auditor for a requirements workspace in a
target project repository.

Goal:
- prevent "quiet drift" (meaning changes without version/changelog),
- prevent missing acceptance criteria,
- reduce ambiguity that would break later JDL/code generation.

## What You Run

From the target repo root:

```powershell
powershell -ExecutionPolicy Bypass -File "<path-to-skill>/scripts/req-audit.ps1" -RootPath requirements
```

Exit codes:
- 0: no errors (warnings may still exist)
- 2: errors found (fix before approval)

## What This Audit Checks

Hard errors:
- missing baseline files: README/INDEX/CHANGELOG/templates
- REQ files missing required headers: Status/Version/Owner/Last Updated + metadata (Type/Level/Parent/Scopes/References/Service)
- REQ missing Non-Goals or Acceptance Criteria (Chinese headings supported)
- Type-specific appendix structure is present (domain-model vs consumer-feature)
- Acceptance checklist exists and covers all AC items (1:1)
- If any REQ is non-DRAFT, a ledger file exists and matches file hashes (prevents untracked drift)
- A ledger file exists and matches file hashes (prevents untracked drift)
- APPROVED REQ has open questions remaining

Warnings:
- ambiguous language in acceptance criteria (e.g., "fast", "secure") without metrics
- INDEX missing entries for REQs

## How to Respond

If audit fails:
- do not proceed to downstream steps (JDL/code/CI)
- update the REQ with explicit constraints/ACs
- add ADRs for decisions that change interpretation
- bump version + update CHANGELOG if meaning changed

## Notes

- The auditor recognizes both English and Chinese labels for common header fields (e.g. `Version`/`版本`),
  and recognizes Chinese section titles like `非目标` and `验收标准`.
- REQ + appendix must remain requirements-level. Do not paste JDL syntax or CI YAML.
- For change tracking, run the authoring skill's `req-ledger.ps1` to update `requirements/.audit/ledger.json` after
  bumping Version and adding a CHANGELOG entry.