Cadence is a planning and verification workflow for developers using Claude Code on software they will keep maintaining. It adds skills for adopting existing repos, capturing todos, auditing requirements before shipping, and configuring review settings.
@crenshawdevInitialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
@crenshawdevRole contract preloaded at spawn by the cad-assumptions-analyzer, cad-assumptions-analyzer-low, cad-assumptions-analyzer-medium,…
@crenshawdevPre-ship traceability audit - every requirement traced to a phase, plan and verification, orphan detection both directions, a…
@crenshawdevCapture a phase-linked todo, a seed idea for a future milestone, or a note, without losing your place - .planning/CAPTURE.md, or…
@crenshawdevConfigure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review…
@crenshawdevGather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass
@crenshawdevFind a completed phase's requirements with no failing-capable test coverage and generate tests to close the gaps, in the…
@crenshawdevSystematic debugging - hypothesis and symptom tracked in a state file that survives /clear, with a user-gated second-model…
@crenshawdevAdversarial refute-then-adjudicate pass over one load-bearing decision - a CONTEXT D-NN line or a PROJECT Key Decisions row -…
@crenshawdevVerify docs claims against the live codebase - paths, commands, symbols, config keys - each reported accurate, stale or…
@crenshawdevExecute a phase's plans - a subagent per plan, an atomic commit per task, a slim per-phase SUMMARY
@crenshawdevRole contract preloaded at spawn by the cad-executor, cad-executor-low, cad-executor-medium, cad-executor-xhigh and…
@crenshawdevThe `xhigh` rung of `cad-assumptions-analyzer` (codebase assumption gathering); `bin/route.mjs` picks it, not the user.
@crenshawdevThe `high` rung of `cad-assumptions-analyzer`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `low` rung of `cad-assumptions-analyzer`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `max` rung of `cad-assumptions-analyzer`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `medium` rung of `cad-assumptions-analyzer`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `high` rung of `cad-executor` (plan task execution); `bin/route.mjs` picks it, not the user.
@crenshawdevThe `low` rung of `cad-executor`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `max` rung of `cad-executor`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `medium` rung of `cad-executor`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `xhigh` rung of `cad-executor`; `bin/route.mjs` picks it, not the user.
@crenshawdevThe `low` rung of `cad-plan-checker` (goal-backward plan gate); `bin/route.mjs` picks it, not the user.
@crenshawdevThe `high` rung of `cad-plan-checker`; `bin/route.mjs` picks it, not the user.
@crenshawdevIs this you? Claim your profilePut a plugin at the top of Plugins, from $9
