agentmods.dev

spec-status

A command that shows the current phase and progress of one or all feature specifications. A specification is a written plan covering requirements, design, implementation tasks, and completion.

In plain words
What is it for?
Checking specification files, workflow phases, completed implementation tasks, and the next recommended action.
Why use it?
It makes it easier to see what has been finished and what work should happen next.

Command

3.9k 11mo ago A scan 0 tokens original MIT
View the source file Pimzino/claude-code-spec-workflow
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/pimzino/claude-code-spec-workflow/spec-status
Clone the repo
git clone --depth 1 https://github.com/Pimzino/claude-code-spec-workflow
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 288 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00288
Opus 5 $0.00000 $0.00144
Sonnet 5 $0.00000 $0.00058
Haiku 4.5 $0.00000 $0.00029

Measured yesterday against content hash 4f663d90c440, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-status 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 yesterday.

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:

src/markdown/commands/spec-status.md · 45 lines

What it actually says

Spec Status Command

Show current status of all specs or a specific spec.

Usage

/spec-status [feature-name]

Instructions

Display the current status of spec workflows.

  1. If no feature-name provided:

    • List all specs in .claude/specs/ directory
    • Show current phase for each spec
    • Display completion status

  2. If feature-name provided:

    • Show detailed status for that spec
    • Display current workflow phase
    • Show completed vs pending tasks
    • List next recommended actions

  3. Status Information:

    • Requirements: [Complete/In Progress/Pending]
    • Design: [Complete/In Progress/Pending]
    • Tasks: [Complete/In Progress/Pending]
    • Implementation: [X/Y tasks complete]

  4. Output Format:

    Spec: user-authentication
Phase: Implementation
Progress: Requirements ✅ | Design ✅ | Tasks ✅
Implementation: 3/8 tasks complete
Next: Execute task 4 - "Implement password validation"

Workflow Phases

  • Requirements: Gathering and documenting requirements
  • Design: Creating technical design and architecture
  • Tasks: Breaking down into implementation tasks
  • Implementation: Executing individual tasks
  • Complete: All tasks finished and integrated
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. yesterday First seen · 45 lines · 0 tokens per session scan A 4f663d90c440

Subscribe to this mod's changes

spec-status is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,853 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 288 tokens. 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-30.

PlanningProductivity
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens