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
Safely undo a phase - roll back its commits from the SUMMARY manifest, revert (or --no-commit to re-do), and reset the phase status
$ npx -y skills add crenshawdev/cadence --skill cad-undo --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-undoContext preview
The summary Claude sees to decide when to auto-load this skill.
Safely undo a phase - roll back its commits from the SUMMARY manifest, revert (or --no-commit to re-do), and reset the phase status
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]" allowed-tools: - Read - Edit - Bash - 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.
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