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
Scanned 9/3/2026
Install to Claude Code
npx -y skills add crenshawdev/cadence --skill cad-suggest --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cad Suggest?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/crenshawdev-cad-suggest)More formats (shields.io, HTML) on the badges page.
---
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>
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!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...