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
Spike - a time-boxed experiment resolving one unknown before you bet on it, risk-first, with a validated | invalidated | inconclusive verdict
$ npx -y skills add crenshawdev/cadence --skill cad-spike --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-spikeContext preview
The summary Claude sees to decide when to auto-load this skill.
Spike - a time-boxed experiment resolving one unknown before you bet on it, risk-first, with a validated | invalidated | inconclusive verdict
name: cad-spike description: "Spike - a time-boxed experiment resolving one unknown before you bet on it, risk-first, with a validated | invalidated | inconclusive verdict" argument-hint: "<the question or hypothesis to resolve>" allowed-tools: - Read - Write - Edit - Bash - Grep - Glob - AskUserQuestion
<objective> Answer one unknown with evidence before a plan commits to it - "will this approach work", "is this library fast enough", "does this API do what we need". The discipline is what makes it useful: falsifiable criteria written BEFORE the experiment, the riskiest assumption tested first so a dead end dies fast, and an honest verdict. The code is throwaway; the SPIKE.md verdict is the deliverable. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/spike.md </execution_context>
<process> Run the spike workflow end-to-end. Write the Given/When/Then criteria before building anything, order them risk-first, and stop the moment a risk-first criterion invalidates the approach. Never soften an invalidated result into "inconclusive" to save the idea - a spike that kills a bad approach is a success. </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