From Cadence
Capture without losing your place - an actionable phase-linked todo (the queue mem-* lacks), a seed idea for a future milestone, or a note. One file: .planning/CAPTURE.md, which the builtin memory backend makes recallable at planning time
How this skill is triggered — by the user, by Claude, or both
Slash command
/cadence:cad-capture [todo | seed | note] <text> [--phase N][todo | seed | note] <text> [--phase N]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
Ensure the file. If .planning/CAPTURE.md is absent, create it with three
headings: ## Todos, ## Seeds, ## Notes.
Append by kind:
- [ ] (phase N) <text> under ## Todos.- <text> under ## Seeds.- <YYYY-MM-DD> <text> under ## Notes. (CAPTURE.md is always
the write path; memory.backend: builtin makes these notes recallable
via planning.mjs recall, and none turns that recall off.)Persist. Stage ONLY .planning/CAPTURE.md and commit docs: capture <kind> (protected-branch guard applies) - this never touches the user's
in-flight changes. Report the one line captured and where.
npx claudepluginhub crenshawdev/cadenceCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.