cad-adopt
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
Safely undo a phase - roll back its commits from the SUMMARY manifest, revert (or --no-commit to re-do), and reset the phase status
Claude Code
$ npx -y skills add crenshawdev/cadence --skill cad-undo --agent claude-code
Codex
$ npx skills add crenshawdev/cadence --skill cad-undo -a codex -y
Cursor
$ npx skills add crenshawdev/cadence --skill cad-undo -a cursor -y
Gemini CLI
$ npx skills add crenshawdev/cadence --skill cad-undo -a gemini-cli -y
GitHub Copilot
$ npx skills add crenshawdev/cadence --skill cad-undo -a github-copilot -y
OpenCode
$ npx skills add crenshawdev/cadence --skill cad-undo -a opencode -y
Windsurf
$ npx skills add crenshawdev/cadence --skill cad-undo -a windsurf -y
name: cad-undo description: "Safely undo a phase - roll back its commits from the SUMMARY manifest, revert (or --no-commit to re-do), and reset the phase status" argument-hint: "<phase N> [--no-commit]" disable-model-invocation: true allowed-tools: - Read - Edit - Grep - Glob - AskUserQuestion
<objective> Undo a phase's work by reverting its commits, using the phase SUMMARY.md as the manifest of exactly which hashes to touch (cad-execute records commits-per-task with hashes there). Safe by construction: never runs on a dirty tree, never guesses. No heuristic dependency-check - instead cad-undo states plainly whether later phases exist and lets the user decide. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/undo.md @${CLAUDE_PLUGIN_ROOT}/cadence-core/references/git-guard.md </execution_context>
<process> Run the undo workflow end-to-end. Refuse on a dirty tree. Show the exact hashes and get confirmation before reverting. Reset the phase's status as part of the rollback (this is the one legitimate exception to cad-verify owning status). </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.