cad-adopt
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
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
Claude Code
$ npx -y skills add crenshawdev/cadence --skill cad-coverage --agent claude-code
Codex
$ npx skills add crenshawdev/cadence --skill cad-coverage -a codex -y
Cursor
$ npx skills add crenshawdev/cadence --skill cad-coverage -a cursor -y
Gemini CLI
$ npx skills add crenshawdev/cadence --skill cad-coverage -a gemini-cli -y
GitHub Copilot
$ npx skills add crenshawdev/cadence --skill cad-coverage -a github-copilot -y
OpenCode
$ npx skills add crenshawdev/cadence --skill cad-coverage -a opencode -y
Windsurf
$ npx skills add crenshawdev/cadence --skill cad-coverage -a windsurf -y
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 - 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 (when `testing.scope` is unset), 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.
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
Role contract preloaded at spawn by the cad-assumptions-analyzer, cad-assumptions-analyzer-low, cad-assumptions-analyzer-medium,…
Pre-ship traceability audit - every requirement traced to a phase, plan and verification, orphan detection both directions, a…
Capture a phase-linked todo, a seed idea for a future milestone, or a note, without losing your place - .planning/CAPTURE.md, or…
Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review…
Gather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.