From Cadence
Systematic debugging - scientific method with hypothesis state persisted across /clear, and a user-gated second-model consult at dead-ends. Single pass, no session-manager layer
How this skill is triggered — by the user, by Claude, or both
Slash command
/cadence:cad-debug [list | status <slug> | continue <slug> | --diagnose] [symptom][list | status <slug> | continue <slug> | --diagnose] [symptom]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>
Routing: parse $ARGUMENTS per the workflow's Route table (debug.md) -
list, status <slug>, continue <slug>, --diagnose, else a new symptom.
The table lives in the workflow, once.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/debug.md </execution_context>
Route on `$ARGUMENTS`, then run the debug workflow single-pass end-to-end. Persist the state file after every hypothesis test and fix attempt. Never auto-loop fixes and never auto-consult - both are deliberate, and the consult is always user-gated.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.