From Cadence
Pre-ship requirement-traceability audit - every requirement traced to a phase, a plan, and a verification; orphan detection both directions; a FAIL gate that catches silently-dropped requirements before a milestone ships
How this skill is triggered — by the user, by Claude, or both
Slash command
/cadence:cad-audit [milestone | defaults to all active requirements][milestone | defaults to all active requirements]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
This is the check that catches the quiet failure a per-phase flow can miss -
a requirement that no phase ever picked up, or one marked done while its phase
never verified. It reads the authoritative status - the REQUIREMENTS
traceability table (Requirement | Phase | Status) and the ROADMAP ## Phases
checkbox, the only persisted status, both written solely by cad-verify. It does
not write status itself.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/audit.md </execution_context>
Run the audit workflow end-to-end and return a clear PASS or FAIL with the evidence. A FAIL is a real gate - report exactly which requirements are untraced, unverified, or orphaned; do not soften it. Read-only: never edit status to make the audit pass.npx claudepluginhub crenshawdev/cadenceCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.