racecraft-plugins-public: Skill for Claude Code

.claude/skills/speckit-resume/SKILL.md

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

A session-resume skill for Specify, a specification-driven development tool, that scans project features and identifies where interrupted work stopped.

In plain words
What is it for?
Use it to detect missing or completed Specify artifacts, count finished and remaining tasks, identify the current phase, and suggest the next Specify command.
Why use it?
It saves developers from manually inspecting specification, planning, task, and checklist files to find the next step.

Skill 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/.claude/skills/speckit-resume/SKILL.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 speckit-resume

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-resume"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 650 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.00019 $0.00650
Opus 5.5 $0.00008 $0.00260
Sonnet 5.5 $0.00004 $0.00130
Haiku 4.5 $0.00002 $0.00065

Measured 1mo ago against content hash e7b613b53897, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speckit-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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/speckit-resume/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 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 · 86 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. 1mo ago First seen · 86 lines · 19 tokens per session scan A e7b613b53897

Subscribe to this mod's changes

speckit-resume is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 650 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

build-executor

Execute an active direct request or approved planned change. Native continuous implementation is the default; existing legacy changes retain their recorded contract obligations.

MageByte-Zero/spec-superflow · 30 tokens

contract-builder

Maintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.

MageByte-Zero/spec-superflow · 33 tokens

codex-issue-coordinator

Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.

owainlewis/blueprint · 59 tokens

plan

Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.

owainlewis/blueprint · 42 tokens

review

Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.

owainlewis/blueprint · 53 tokens

html-doc

Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, visualize, or make a PRD or design document easier for humans to read in a browser.

owainlewis/blueprint · 51 tokens