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
Render a phase's run record as a receipts narrative - what each dispatch cost, what the gates caught, what got refuted - straight from trace.jsonl and the phase artifacts
$ npx -y skills add crenshawdev/cadence --skill cad-report --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-reportContext preview
The summary Claude sees to decide when to auto-load this skill.
Render a phase's run record as a receipts narrative - what each dispatch cost, what the gates caught, what got refuted - straight from trace.jsonl and the phase artifacts
name: cad-report description: "Render a phase's run record as a receipts narrative - what each dispatch cost, what the gates caught, what got refuted - straight from trace.jsonl and the phase artifacts" argument-hint: "[phase] [--all]" allowed-tools: - Read - Bash - Grep - Glob
<objective> Turn `.planning/trace.jsonl` and a phase's artifacts into the story of what your tokens bought: every dispatch priced, every gate's outcome named, every refuted assumption cited. Read-only - it renders the record, it never writes it. `--all` spans the whole record for a milestone-shaped view. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/report.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