cad-adopt
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
CRUD phases in ROADMAP - add, insert, remove, edit, with remove/insert renumbering the following phases, their .planning dirs and their live references, while insert and remove leave shipped requirement rows as written
Claude Code
$ npx -y skills add crenshawdev/cadence --skill cad-phase --agent claude-code
Codex
$ npx skills add crenshawdev/cadence --skill cad-phase -a codex -y
Cursor
$ npx skills add crenshawdev/cadence --skill cad-phase -a cursor -y
Gemini CLI
$ npx skills add crenshawdev/cadence --skill cad-phase -a gemini-cli -y
GitHub Copilot
$ npx skills add crenshawdev/cadence --skill cad-phase -a github-copilot -y
OpenCode
$ npx skills add crenshawdev/cadence --skill cad-phase -a opencode -y
Windsurf
$ npx skills add crenshawdev/cadence --skill cad-phase -a windsurf -y
name: cad-phase description: "CRUD phases in ROADMAP - add, insert, remove, edit, with remove/insert renumbering the following phases, their .planning dirs and their live references, while insert and remove leave shipped requirement rows as written" argument-hint: "add [description] | insert <N> | remove <N> | edit <N>" allowed-tools: - Read - Write - Edit - 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 whose live references have to follow or the project's references rot. Shipped requirement rows are history: insert and remove leave them as written. This skill keeps the live references 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 live references out of sync, and never hand-shift a requirement row the seam left as written. </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.
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
Role contract preloaded at spawn by the cad-assumptions-analyzer, cad-assumptions-analyzer-low, cad-assumptions-analyzer-medium,…
Pre-ship traceability audit - every requirement traced to a phase, plan and verification, orphan detection both directions, a…
Capture a phase-linked todo, a seed idea for a future milestone, or a note, without losing your place - .planning/CAPTURE.md, or…
Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review…
Gather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.