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
Project progress - count-based status from files and git, finds incomplete or paused work and offers to resume it, --stats for a quick summary
$ npx -y skills add crenshawdev/cadence --skill cad-progress --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-progressContext preview
The summary Claude sees to decide when to auto-load this skill.
Project progress - count-based status from files and git, finds incomplete or paused work and offers to resume it, --stats for a quick summary
name: cad-progress description: "Project progress - count-based status from files and git, finds incomplete or paused work and offers to resume it, --stats for a quick summary" argument-hint: "[--stats|--trace]" allowed-tools: - Read - Write - Bash - Grep - Glob - AskUserQuestion - SlashCommand
<objective> Answer "where am I and what's next" for the current Cadence project. Truth is derived by counting: ROADMAP.md phases vs phases/<N>/ artifacts (PLAN.md, SUMMARY.md, UAT.md fully passed) plus recent git log. STATE.md is a hint, not a source. Detects incomplete or paused work and offers to resume at the right step, routing to the spine skill that does it (/cad-context, /cad-plan, /cad-execute, /cad-verify, /cad-milestone, /cad-phase add between milestones) - never does the work itself. `--stats` prints a summary derived on demand; `--trace` prints the current phase's joined run record - routing, provider, worker-lifecycle and outcome events - and writes nothing. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/progress.md </execution_context>
<process> Execute end-to-end. </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