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
CRUD phases in ROADMAP - add, insert, remove, edit, with remove/insert renumbering the following phases, their .planning dirs and every phase reference
$ npx -y skills add crenshawdev/cadence --skill cad-phase --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-phaseContext preview
The summary Claude sees to decide when to auto-load this skill.
CRUD phases in ROADMAP - add, insert, remove, edit, with remove/insert renumbering the following phases, their .planning dirs and every phase reference
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>
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…
Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review provider setup
Gather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass