cad-adopt
Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from…
@crenshawdevInstall SkillDevelopment
Skill
/cad-milestone
Cut a milestone - audit that nothing was dropped, bump a release's version, prune completed phases from the roadmap, evolve PROJECT and refresh REQUIREMENTS
Claude Code
$ npx -y skills add crenshawdev/cadence --skill cad-milestone --agent claude-code
Codex
$ npx skills add crenshawdev/cadence --skill cad-milestone -a codex -y
Cursor
$ npx skills add crenshawdev/cadence --skill cad-milestone -a cursor -y
Gemini CLI
$ npx skills add crenshawdev/cadence --skill cad-milestone -a gemini-cli -y
GitHub Copilot
$ npx skills add crenshawdev/cadence --skill cad-milestone -a github-copilot -y
OpenCode
$ npx skills add crenshawdev/cadence --skill cad-milestone -a opencode -y
Windsurf
$ npx skills add crenshawdev/cadence --skill cad-milestone -a windsurf -y
SKILL.md
cad-milestone.SKILL.mdname: cad-milestone
description: "Cut a milestone - audit that nothing was dropped, bump a release's version, prune completed phases from the roadmap, evolve PROJECT and refresh REQUIREMENTS"
argument-hint: "[version | next-milestone name]"
allowed-tools:
- Read
- Write
- Edit
- Grep
- Glob
- Task
- AskUserQuestion
- SlashCommand
<objective> Close a finished milestone and set up the next. Thin by design - it collapses new-milestone + complete-milestone + cleanup into one flow. It tags the release only when the project tags (non-release projects skip it), it never ships (publishing a tag is /cad-land's call), and it never cuts a milestone that silently dropped a requirement (cad-audit gates it). </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/milestone.md @${CLAUDE_PLUGIN_ROOT}/cadence-core/references/git-guard.md </execution_context>
<process> Run the milestone workflow end-to-end. The audit gate is real - do not tag a milestone with a failing traceability audit unless the user explicitly overrides. Prune from the working tree only (git keeps the history); never auto-push the tag. Under `git.auto_close` (default off), chain into `/cad-land` to complete the close (PR -> merge -> reset), still halting on a surviving blocker/high `risk_surface` finding; otherwise stop at the tag and leave publishing to a separate `/cad-land`. </process>
Read more
name: cad-milestone description: "Cut a milestone - audit that nothing was dropped, bump a release's version, prune completed phases from the roadmap, evolve PROJECT and refresh REQUIREMENTS" argument-hint: "[version | next-milestone name]" allowed-tools: - Read - Write - Edit - Grep - Glob - Task - AskUserQuestion - SlashCommand
<objective> Close a finished milestone and set up the next. Thin by design - it collapses new-milestone + complete-milestone + cleanup into one flow. It tags the release only when the project tags (non-release projects skip it), it never ships (publishing a tag is /cad-land's call), and it never cuts a milestone that silently dropped a requirement (cad-audit gates it). </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/milestone.md @${CLAUDE_PLUGIN_ROOT}/cadence-core/references/git-guard.md </execution_context>
<process> Run the milestone workflow end-to-end. The audit gate is real - do not tag a milestone with a failing traceability audit unless the user explicitly overrides. Prune from the working tree only (git keeps the history); never auto-push the tag. Under `git.auto_close` (default off), chain into `/cad-land` to complete the close (PR -> merge -> reset), still halting on a surviving blocker/high `risk_surface` finding; otherwise stop at the tag and leave publishing to a separate `/cad-land`. </process>
Ships withcadence
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.
834 skills30 agents
Stars on GitHub
Momentum
- stars in total
- 8
Other skills on cadence.
@crenshawdevInstall Skillcad-assumptions-analyz…
Role contract preloaded at spawn by the cad-assumptions-analyzer, cad-assumptions-analyzer-low, cad-assumptions-analyzer-medium,…
@crenshawdevInstall Skillcad-audit
Pre-ship traceability audit - every requirement traced to a phase, plan and verification, orphan detection both directions, a…
@crenshawdevInstall Skillcad-capture
Capture a phase-linked todo, a seed idea for a future milestone, or a note, without losing your place - .planning/CAPTURE.md, or…
@crenshawdevInstall Skillcad-config
Configure Cadence's config.json - workflow toggles, the per-role model and effort interview, and interactive cross-model review…
@crenshawdevInstall Skillcad-context
Gather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass
@crenshawdevInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about cad-milestone.
- Which coding agents can use cad-milestone?
- cad-milestone installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.