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
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
$ npx -y skills add crenshawdev/cadence --skill cad-coverage --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-coverageContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: cad-coverage description: "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" argument-hint: "[phase number]" allowed-tools: - Read - Write - Edit - Bash - Grep - Glob - AskUserQuestion
<objective> Close the test-coverage gaps for a completed phase. One question drives it: which phase requirements have NO test that would fail if that requirement regressed? Those are the gaps. Audit them, then generate real tests to cover them, in the project's own test framework.
Audit and generate in one un-duplicated flow. No fixed stack, no Playwright/E2E default - the test kind and runner follow the code and `workflow.test_command`. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/coverage.md </execution_context>
<process> Run the coverage workflow end-to-end. Coverage means a test that would FAIL if the requirement broke - not a test that merely runs the code. Get user approval on the gap test plan before generating, and verify generated tests actually run. </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