cad-adopt
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from the code and the git history
Turn the run record into evidence-backed retune suggestions - each with its config key, the value in force, a direction and a target - and offer to route the ones you accept to /cad-config
$ npx -y skills add crenshawdev/cadence --skill cad-suggest --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-suggestContext preview
The summary Claude sees to decide when to auto-load this skill.
Turn the run record into evidence-backed retune suggestions - each with its config key, the value in force, a direction and a target - and offer to route the ones you accept to /cad-config
name: cad-suggest description: "Turn the run record into evidence-backed retune suggestions - each with its config key, the value in force, a direction and a target - and offer to route the ones you accept to /cad-config" argument-hint: "[phase]" allowed-tools: - Bash - SlashCommand
<objective> The retune the run record supports, read back to you: every tweak under a heading of its own carrying its config key, the value in force, the direction to move it and the target where the record prices one, with the receipts that ask for nothing kept separate below. Every figure comes from `planning.mjs trace suggest` - this command relays the record, it never recomputes it and it writes no config key itself. It ends by offering to route the tweaks you accept to `/cad-config`, which is where a write would happen. No argument spans the whole record; a phase number scopes it. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/suggest.md </execution_context>
<process> Execute end-to-end. </process>
Appearance is cheap. Verification is the work. Cadence is for developers using Claude Code on software they will still own after the session ends. Claude can write a convincing plan, produce working code, and tell you the job is finished.
Repo: crenshawdev/cadence
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from the code and the git history
Internal role contract, preloaded into every cad-assumptions-analyzer rung agent. Not a user command.
Pre-ship traceability audit - every requirement traced to a phase, plan and verification, orphan detection both directions, a FAIL gate before shipping
Capture a phase-linked todo, a seed idea for a future milestone, or a note, without losing your place - .planning/CAPTURE.md, or --cadence for friction with…
Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review provider setup
Gather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass