cad-adopt
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
Verify a completed phase by conversational UAT - a persistent checklist that survives /clear, plus cross-phase and goal-backward passes
Claude Code
$ npx -y skills add crenshawdev/cadence --skill cad-verify --agent claude-code
Codex
$ npx skills add crenshawdev/cadence --skill cad-verify -a codex -y
Cursor
$ npx skills add crenshawdev/cadence --skill cad-verify -a cursor -y
Gemini CLI
$ npx skills add crenshawdev/cadence --skill cad-verify -a gemini-cli -y
GitHub Copilot
$ npx skills add crenshawdev/cadence --skill cad-verify -a github-copilot -y
OpenCode
$ npx skills add crenshawdev/cadence --skill cad-verify -a opencode -y
Windsurf
$ npx skills add crenshawdev/cadence --skill cad-verify -a windsurf -y
name: cad-verify description: "Verify a completed phase by conversational UAT - a persistent checklist that survives /clear, plus cross-phase and goal-backward passes" argument-hint: "[phase] [--sweep] [--deep]" allowed-tools: - Read - Write - Edit - Grep - Glob - AskUserQuestion - Task - Workflow - Workflow(cadence:review-panel)
<objective> Walk the user through a phase's acceptance criteria one item at a time, recording pass/fail/skip in a persistent .planning/phases/<N>/UAT.md. Results survive /clear and session ends - re-run to resume at the first untested item. Failures are diagnosed and routed through the normal Cadence flow (user-approved atomic fix commit, or /cad-plan for phase-sized gaps) - no internal auto-fixer loop. `--sweep` scans every phase's UAT file and reports what is still outstanding. `--deep` spawns cad-verifier for a goal-backward check of what the code actually delivers. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/verify.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.
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.