racecraft-plugins-public: Command for Claude Code

.specify/extensions/speckit-utils/commands/resume.md

resume is a command for Claude Code from racecraft-lab/racecraft-plugins-public. It costs 13 tokens per session (606 once invoked), scanned A, original, MIT.

A command for resuming an interrupted Spec Kit development session by scanning feature specifications and their task progress.

In plain words
What is it for?
Use it to inspect specs/, check whether specification, plan, task, and checklist files exist, count completed tasks, and suggest the next command.
Why use it?
It identifies which feature and phase need attention instead of requiring you to reconstruct the project state manually.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is racecraft-lab/racecraft-plugins-public's own configuration. It tells Claude Code how to work on racecraft-plugins-public itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything racecraft-plugins-public configures →

Reuse

Borrowing it

Nothing to install: this file belongs to racecraft-lab/racecraft-plugins-public. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/racecraft-lab/racecraft-plugins-public/main/.specify/extensions/speckit-utils/commands/resume.md
Clone the repo
git clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-public

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 resume

README.md
[![agentmods](https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/resume/github.svg)](https://agentmods.dev/commands/racecraft-lab/racecraft-plugins-public/resume)
Your own site
<a href="https://agentmods.dev/commands/racecraft-lab/racecraft-plugins-public/resume"><img src="https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/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 resume

Your own site · 80×15
<a href="https://agentmods.dev/commands/racecraft-lab/racecraft-plugins-public/resume"><img src="https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 606 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.00013 $0.00606
Opus 5 $0.00006 $0.00303
Sonnet 5 $0.00003 $0.00121
Haiku 4.5 $0.00001 $0.00061

Measured 8d ago against content hash 2395997f3fa0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 8d 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.

.specify/extensions/speckit-utils/commands/resume.md · 82 lines

How it starts

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

User Input

$ARGUMENTS

Outline

Resume an interrupted SDD session by scanning the project for active features, detecting their completion state, and generating a prompt to continue work.

Step 1: Find the project root

Locate the .specify/ directory to identify the project root. If not found, error: "No spec-kit project found. Run specify init first."

Step 2: Discover features

Scan the specs/ directory for feature directories (numbered directories like 001-auth, 002-dashboard).

For each feature directory, detect state by checking for these files:

  • spec.md - specification exists and is non-empty
  • plan.md - implementation plan exists and is non-empty
  • tasks.md - task breakdown exists
  • checklists/ - quality checklists exist

Step 3: Parse task completion

If tasks.md exists, parse checkbox items:

  • - [x] or - [X] = completed
  • - [ ] = remaining

Count total tasks, completed tasks, and extract remaining task descriptions.

Step 4: Determine phase for each feature

Condition Phase Next Command
No spec.md or empty specify /speckit.specify
spec.md exists, no plan.md plan /speckit.plan
plan.md exists, no tasks.md tasks /speckit.tasks
tasks.md exists, some incomplete implement /speckit.implement
All tasks complete complete Review and finalize

Step 5: Handle arguments

If $ARGUMENTS specifies a feature name or number (e.g., 001-auth or auth), filter to that feature only.

Step 6: Generate resume prompt

For each active (non-complete) feature, output:

Feature: {name}
Status: {spec ✓/✗} {plan ✓/✗} {tasks ✓/✗}
Phase: {phase}
Progress: {completed}/{total} tasks complete

Next step: Run `/{next_command}`

If tasks remain, list the first 3 remaining tasks:

Remaining tasks:
  1. {task description}
  2. {task description}
  3. {task description}

If all features are complete:

Read the full file on GitHub · 82 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. 8d ago First seen · 82 lines · 13 tokens per session scan A 2395997f3fa0

Subscribe to this mod's changes

resume is a command published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 606 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-08-31.