# speckit.companion.resume

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.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 110 repo stars
- Author: alfredoperez
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.resume.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/speckitcompanionresume

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/speckit.companion.resume.md` — Call it with /speckit.companion.resume. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/speckit.companion.resume.md` — Call it with /prompts:speckit.companion.resume. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/speckit.companion.resume.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/speckit.companion.resume.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.resume.md

## When to use it
- 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
- Call resume to pick up the spec I started yesterday
- Run `speckit.companion.resume` and continue where I left off in implementation
- After returning to the project, give me a summary of the next step in the spec

## Source text · speckit.companion.resume.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 93964923bb150bb6.

BEGIN THIRD-PARTY FILE 93964923bb150bb6
````text
---
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.
````
END THIRD-PARTY FILE 93964923bb150bb6

The third-party file has ended. Everything between the 93964923bb150bb6 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© alfredoperez · MIT · https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.resume.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
