From Cadence
Verify factual claims in docs against the live codebase - file paths, commands, code symbols, config keys, structure - and report which are accurate, stale, or unverifiable. Reports; it does not rewrite docs
How this skill is triggered — by the user, by Claude, or both
Slash command
/cadence:cad-docs-verify [path or glob | defaults to README + docs/][path or glob | defaults to README + docs/]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 docs-verifier engine only; the doc WRITER is collapsed out (DESIGN §2). cad-docs-verify never rewrites a doc - it produces the findings a human (or a later edit) acts on.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/docs-verify.md </execution_context>
Run the verify workflow end-to-end. Only claim `stale` when the code actually contradicts the doc; when a claim cannot be checked mechanically, mark it `unverifiable` rather than guessing. Do not edit any doc.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.