Skip to content
Development
Skill

/cad-pause

Pause work cleanly - a WIP commit of in-flight changes plus a STATE cursor set to paused with a one-line resume pointer (/cad-progress offers to resume it)

From plugin
cadence
534 skills30 agents3 hooks
Install
$ npx -y skills add crenshawdev/cadence --skill cad-pause --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/cad-pause

Context preview

The summary Claude sees to decide when to auto-load this skill.

Pause work cleanly - a WIP commit of in-flight changes plus a STATE cursor set to paused with a one-line resume pointer (/cad-progress offers to resume it)

SKILL.md

cad-pause.SKILL.md
name: cad-pause
description: "Pause work cleanly - a WIP commit of in-flight changes plus a STATE cursor set to paused with a one-line resume pointer (/cad-progress offers to resume it)"
argument-hint: "[one-line note about where you are]"
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash
  - AskUserQuestion

<objective> Stop mid-work without losing the thread. Two small acts: commit the in-flight changes as WIP so nothing is lost, and write the STATE cursor so the next session (via /cad-progress, which finds it and offers to resume) knows exactly where to pick up. Tiny by design - no Stop hook, no handoff document, no activity log. </objective>

<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/references/git-guard.md </execution_context>

<process> 1. **WIP commit.** If the tree has changes, stage exactly what the user was working on and commit `wip: <short description>` (protected-branch guard applies - references/git-guard.md). If the tree is clean, skip this; there is nothing to preserve.

2. **Set the cursor** through the seam (never hand-edit STATE.md):

   node "${CLAUDE_PLUGIN_ROOT}/cadence-core/bin/planning.mjs" cursor set \
     --phase <current> --status paused --next-file <path>

The resume pointer is a one-line "where I was" naming the next concrete action (from `$ARGUMENTS`, or ask via the ask-user seam if not given) - the user's own sentence, so write it to a scratch file and pass the PATH (caller-derived text - references/conventions.md). This line IS the pause note /cad-progress surfaces. `--phase <current>` is required - the seam does NOT preserve a prior `Phase:` (it fails `bad-args` without it); supply the current phase from `cursor get`, which goes in one message with step 1's protected-branch git probes - they are independent, and only a call that consumes a prior call's output is serialized. The seam derives name/total from ROADMAP and stamps `Updated:` itself. Commit the cursor (`docs:`), or fold it into the WIP commit if one was made. Never leave the tree dirty.

3. **Report.** One line: paused at <phase>, resume with /cad-progress. </process>

Read more
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.

Get the whole plugin

Other skills on cadence.