agentmods.dev

speckit.companion.resume

speckit.companion.resume is a command for Claude Code from alfredoperez/speckit-companion. It costs 22 tokens per session (845 once invoked), scanned A, original, MIT.

A command that continues a spec-driven development workflow from its last completed phase, carrying recorded decisions into the next step.

In plain words
What is it for?
Use it to resume specification, planning, task creation, or implementation, including the next unchecked task during implementation.
Why use it?
It removes the need to determine manually where an interrupted workflow stopped and which command should run next.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 .specify/extensions/companion/scripts/status-context.py.

not rated 90repo +3 changed 2d ago A scan 22 tokens original MIT

Good fit Use it to resume specification, planning, task creation, or implementation, including the next unchecked task during implementation.

Compare 6 commands from other repositories ↓
View source ↗ alfredoperez/speckit-companion speckit-companion.dev
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/alfredoperez/speckit-companion
agentmods
npx agentmods add commands/alfredoperez/speckit-companion/speckit.companion.resume

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for speckit.companion.resume

README.md
[![agentmods](https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.resume/github.svg)](https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.companion.resume)
Your own site
<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.companion.resume"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.resume/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for speckit.companion.resume

Your own site · 80×15
<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.companion.resume"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 845 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00845
Opus 5 $0.00011 $0.00423
Sonnet 5 $0.00004 $0.00169
Haiku 4.5 $0.00002 $0.00085

Measured 2d ago against content hash f73bd6ac643d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

speckit.companion.resume scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

speckit-extension/commands/speckit.companion.resume.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

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.

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:

    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).

Read the full file on GitHub · 80 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago Changed · +6 lines f73bd6ac643d
  2. 9d ago First seen · 74 lines · 22 tokens per session scan A e24f01a71fb7

Subscribe to this mod's changes

speckit.companion.resume is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 845 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Claude CodePlanningTypeScriptai-toolsdeveloper-toolsspec-driven-developmentvscode-extension
Related

Other commands, from other repositories

migrate-to-typescript

Migrate JavaScript project to TypeScript.

qdhenry/Claude-Command-Suite · 0 tokens

svelte:component

Create new Svelte components with best practices, proper structure, and optional TypeScript support.

qdhenry/Claude-Command-Suite · 0 tokens

autospec.plan

Generate YAML implementation plan from feature specification.

ariel-frischer/autospec · 8 tokens

code-locate

Given a behavior description, locate candidate code paths and line ranges in the active codebase that probably implement it. Output up to 10 candidates with HIGH/MEDIUM/LOW confidence, one-line rationale per candidate, and an explicit search trail; propose a SOURCEOFTRUTH.md update so the next workflow step (typically…

Mozurok/fhorja.dev · 209 tokens

harvest-session-learnings

Scan the current working session and the active task's artifacts for reusable, generalizable lessons (what was tried, what failed and why, what surprised us, what the next task should do differently) and propose anchored entries to append to the task's LEARNINGS.md, the produce-side counterpart to the ADR-0017 consume…

Mozurok/fhorja.dev · 198 tokens

screen-spec

Generate a screen specification from a Figma frame using MCP tools (getdesigncontext, getscreenshot). Produces a spec doc matching the SCREENSPEC.md template with layout sketch, components used, spacing observed, data dependencies, copy, accessibility notes, interactions, and error states. Use when documenting a…

Mozurok/fhorja.dev · 114 tokens