speckit.companion.resume — Claude Code command: resume spec pipeline
speckit.companion.resume is a command for Claude Code that resumes spec-driven development after a pause. It carries recorded decisions forward and starts the next pipeline step.
MIT ★ 110 updated 2026-10-19
.claude/commands/speckit.companion.resume.mdWhat speckit.companion.resume does
This command works within spec-kit, a framework for stepwise design via specs. When development pauses at any stage—plan, tasks, or implementation—speckit.companion.resume recovers progress: it reads .spec-context.json or reconstructs state from disk, identifies where work halted, and carries all recorded decisions into context for the next command.
Here's how it works: a status-context.py script parses the saved state and returns instructions. If the pipeline is complete, resume stops. If unchecked tasks remain in the implementation phase, resume invokes speckit.implement pointing to the next task. Otherwise, resume calls the appropriate command: speckit.plan, speckit.tasks, or similar.
Requires Python 3 in PATH. If unavailable, the command prints a warning and exits gracefully without breaking the host.
What it helps with
- resume development from a saved spec after stepping away
- carry forward decisions and context into the next pipeline step
- continue implementation at the next unchecked task
- avoid re-entering parameters and context when recovering work
Example prompts for the agent
- Call resume to pick up the spec I started yesterday
- Run
speckit.companion.resumeand continue where I left off in implementation - After returning to the project, give me a summary of the next step in the spec
How to install speckit.companion.resume
Manually: put the files in place
.claude/commands/speckit.companion.resume.mdCall it with /speckit.companion.resume. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/speckit.companion.resume.mdCall it with /prompts:speckit.companion.resume. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/speckit.companion.resume.prompt.mdManually: put the files in place
.gemini/commands/speckit.companion.resume.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about speckit.companion.resume
How do I install speckit.companion.resume in Claude Code?
Copy the file .claude/commands/speckit.companion.resume.md into .claude/commands/ in your project if it is not already there. Claude Code will automatically register it as /speckit-companion-resume.
What does speckit.companion.resume do?
It reads the saved spec state, restores all recorded decisions into scope, and automatically runs the next command in the pipeline—whether that is plan, tasks, or implementation. If tasks remain in the implement phase, resume continues at the next unchecked task.
What is required for the command to work?
Your project must have spec-kit initialized with state (a specs/ directory containing features and a .spec-context.json file or on-disk state). Python 3 must be available in PATH; if not, the command prints a warning and exits safely.
Source text
speckit.companion.resume.md · MIT
---
description: "Continue the spec-driven pipeline from the last completed step, carrying recorded decisions into scope, and dispatch the next command"
---
# Resume Spec
Pick the pipeline back up where it stopped. This command reads the active
feature's recorded state, resolves the next step — carrying the recorded
`decisions` into scope — and dispatches the next `speckit.*` command. Inside the
implement step it continues at the next unchecked task.
<!-- speckit-companion:part command-spelling -->
## Name every command the way this project registers it
Commands are named in dot form throughout this body, `speckit.companion.plan`, because that is their canonical id, and without a leading slash, because the spelling a host actually registers is not always this one. Claude Code installs `/speckit-companion-plan`. Look at how the commands are installed in this project, under the agent's own commands or skills directory, and use that spelling every time you name one to the developer or dispatch one yourself. A dotted name typed into a host that registered dashes resolves to nothing at all.
<!-- /speckit-companion:part command-spelling -->
## Prerequisites
- Verify Python is available by running `python3 --version`.
- If `python3` is not available, warn the user and skip:
`[companion] Warning: python3 not detected; skipped resume`.
Do not fail the host command.
## Execution
1. Resolve the next action from the repository root:
```bash
python3 .specify/extensions/companion/scripts/status-context.py
```
(Pass `--feature-dir specs/<NNN>-<slug>` when you already know it.) The script
reads `.spec-context.json`, or derives state from on-disk files when it is
missing/malformed.
2. Parse the final `RESOLUTION: { … }` JSON line the script prints. It contains
`currentStep`, `status`, `decisions[]`, `nextStep`, `nextCommand`,
`nextActionLabel`, `nextTask`, and `complete`.
3. Branch on the resolution:
- **`complete: true`** → print `Pipeline complete — nothing to resume.` and stop.
Do not dispatch anything.
- **`empty: true`** (no recorded state and no spec files) → print
`Nothing to resume (no spec files or recorded state found).` and stop.
- **`nextTask` is set** (inside the implement step) → continue implementation at
`nextTask`: invoke `speckit.implement`, instructing it to resume at the next
unchecked task.
- **otherwise** → invoke `nextCommand` (e.g. `speckit.plan`, `speckit.tasks`,
`speckit.implement`).
4. When you dispatch, state the recorded `decisions[]` as in-scope context for the
step you are running, so prior decisions carry forward and the user does not
re-specify them.
## Dispatch note
Resume dispatches the **already-installed** `speckit.*` commands. It does not
require a `specify workflow resume` CLI subcommand, so it works on the stock
installed spec-kit version. The dispatched command runs its own `after_*` capture
hook, which writes the resulting `history[]` entry — resume itself writes no state.
## Output
```text
Resuming <name> from <currentStep> (<status>).
Decisions in scope:
- <decision>
Next: <action> → dispatching <command>
```
- Tasks/implement step → `Next: Continue implementation at <task> → dispatching speckit.implement`.
- No decisions recorded → omit the "Decisions in scope" block.
## Graceful Degradation
Best-effort: if `python3` is missing or the feature directory cannot be resolved,
warn to stderr and stop without dispatching. Never fail the host command.
© alfredoperez · MIT · alfredoperez/speckit-companion