Configure Cadence's config.json - workflow toggles, routing stakes, and interactive cross-model review provider setup
Scanned 9/3/2026
Install to Claude Code
npx -y skills add crenshawdev/cadence --skill cad-config --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cad Config?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/crenshawdev-cad-config)More formats (shields.io, HTML) on the badges page.
---
name: cad-config
description: "Configure Cadence's config.json - workflow toggles, routing stakes, and interactive cross-model review provider setup"
argument-hint: "[--review [redetect] | --surfaces | <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:
- **--review [redetect]**: run the cross-model review-provider setup - detect
each provider's accessible models and assign them to the flagship/balanced/
cheap tiers.
- **--surfaces**: re-open the one-time risk-surface question - the answered set
beside what the structure evidences now, re-answerable or declinable.
- **`<key>=<value>` ...**: set config keys directly (validated against the config schema).
- **default** (no args): walk every knob as a selectable list (batched pages),
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>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!