cad-assumptions-analyz…
Internal role contract, preloaded into every cad-assumptions-analyzer rung agent. Not a user command.
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
$ npx -y skills add crenshawdev/cadence --skill cad-adopt --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-adoptContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: cad-adopt description: "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" argument-hint: "" allowed-tools: - Read - Write - Edit - Bash - Grep - Glob - AskUserQuestion
<objective> The second front door. A project that already has code and history enters Cadence as itself instead of as a blank page: the README, the manifests, the tree and `git log` are read here, shipped capability lands in PROJECT.md as Validated, the roadmap covers what is LEFT, and the only questions asked are the ones the repo cannot answer. What it writes is the same `.planning/` shape /cad-new-project writes, so every downstream command works unchanged. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/adopt.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
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
Find a completed phase's requirements with no failing-capable test coverage and generate tests to close the gaps, in the project's own framework