CRUD phases in ROADMAP - add, insert, remove, edit, with remove/insert renumbering the following phases, their .planning dirs and every phase reference
Scanned 9/3/2026
Install to Claude Code
npx -y skills add crenshawdev/cadence --skill cad-phase --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cad Phase?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/crenshawdev-cad-phase)More formats (shields.io, HTML) on the badges page.
---
name: cad-phase
description: "CRUD phases in ROADMAP - add, insert, remove, edit, with remove/insert renumbering the following phases, their .planning dirs and every phase reference"
argument-hint: "add [description] | insert <N> | remove <N> | edit <N>"
allowed-tools:
- Read
- Write
- Edit
- Bash
- Grep
- Glob
- AskUserQuestion
---
<objective>
Edit the phase list in ROADMAP.md safely. `add` and `edit` are near-trivial
markdown changes; `insert` and `remove` are not - they shift phase numbers, and
a phase number lives in four places that must move together or the project's
references rot. This skill keeps them consistent.
</objective>
<execution_context>
@${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/phase.md
@${CLAUDE_PLUGIN_ROOT}/cadence-core/references/git-guard.md
</execution_context>
<process>
Route on `$ARGUMENTS` (add | insert N | remove N | edit N) and run the phase
workflow. For insert/remove, do the full renumber-and-repair pass - never edit
ROADMAP alone. Commit the change atomically (protected-branch guard applies);
never leave phase dirs and references out of sync.
</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', ...