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
Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review provider setup
$ npx -y skills add crenshawdev/cadence --skill cad-config --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-configContext preview
The summary Claude sees to decide when to auto-load this skill.
Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review provider setup
name: cad-config description: "Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review provider setup" argument-hint: "[--review [redetect] | --surfaces | --roles [--global] | <key>=<value> ...]" allowed-tools: - Read - Write - Edit - Bash - AskUserQuestion
<objective> Manage `.planning/config.json` (template in `cadence-core/templates/config.json`). One skill for the whole config; its substantive part is review-provider model assignment, which needs live detection (call the provider models endpoint, classify, assign per tier).
Routing:
each provider's accessible models and assign them to the flagship/balanced/ cheap tiers.
beside what the structure evidences now, re-answerable or declinable.
roles costs - a model and a start rung per role, then the risk floor. Writes repo-layer diffs by default; `--global` re-enters the full thirteen against the user-global layer.
each preselected to its current value. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/config.md </execution_context>
<process> Parse `$ARGUMENTS`, then execute the matching branch of the config workflow end-to-end. Never write an invalid config; never block the spine on a network call (detection degrades to claude-subagent). </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…
Gather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass
Find a completed phase's requirements with no failing-capable test coverage and generate tests to close the gaps, in the project's own framework