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
Initialize a project through deep questioning - PROJECT.md, REQUIREMENTS.md, a phased ROADMAP.md and .planning/ state
$ npx -y skills add crenshawdev/cadence --skill cad-new-project --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cad-new-projectContext preview
The summary Claude sees to decide when to auto-load this skill.
Initialize a project through deep questioning - PROJECT.md, REQUIREMENTS.md, a phased ROADMAP.md and .planning/ state
name: cad-new-project description: "Initialize a project through deep questioning - PROJECT.md, REQUIREMENTS.md, a phased ROADMAP.md and .planning/ state" argument-hint: "[--research] [--brief <file>]" allowed-tools: - Read - Write - Edit - Bash - Grep - Glob - AskUserQuestion - Task
<objective> Start a project properly: question deeply until the idea is concrete, then write PROJECT.md and REQUIREMENTS.md, derive a phased ROADMAP.md with falsifiable per-phase success criteria, and initialize .planning/ (config copied from the engine template, STATE.md cursor). Research is off by default; `--research` or config `workflow.research` enables a single research pass. `--brief <file>` reads a design brief an earlier conversation produced and questions only what it leaves open. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/new-project.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
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