README

A set of Claude Code slash commands for the Spec-Flow workflow, which turns a feature idea into specifications, plans, tasks, and implementation steps. It provides commands for starting, checking, and moving through that workflow.

In plain words
What is it for?
Use it to create feature specifications, clarify unclear requirements, make implementation plans, manage tasks, run quick changes, and check workflow state.
Why use it?
It gives a shared process for organising feature work instead of keeping requirements and progress only in conversation or memory.

Command for Claude Code

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/marcusgoll/spec-flow/readme
Clone the repo
git clone --depth 1 https://github.com/marcusgoll/Spec-Flow

Made for: Claude Code.

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 3,488 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.03488
Opus 5 $0.00000 $0.01744
Sonnet 5 $0.00000 $0.00698
Haiku 4.5 $0.00000 $0.00349

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

Security

Grade A, and why

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

.claude/commands/README.md · 389 lines

How it starts

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

Slash Commands Reference

Location: .claude/commands/ Purpose: Claude adapter surfaces for the Spec-Flow workflow

All commands can be invoked via /command-name in Claude Code. These files are primarily adapter surfaces over the shared execution engine in .spec-flow/scripts/, with tool-specific instructions where Claude requires them.


Command Index by Category

Core Workflow Commands

Primary orchestrators that users interact with directly

Command Description Status Version
/feature Create and orchestrate complete feature workflow ✅ Stable -
/help Show contextual workflow state and next steps ✅ Stable -
/quick Quick implementation (skip spec/plan/tasks for small changes) ✅ Stable -
/route-agent Internal helper to route tasks to specialist agents ⚙️ Internal -

Phase Commands

Sequential workflow phases (invoked by /feature or manually)

Command Description Status Version Refactor
/spec Create feature specification from natural language ✅ Stable v2.0 ✅ Done
/clarify Reduce spec ambiguity via targeted questions ✅ Stable v2.0 ✅ Done
/plan Generate design artifacts from feature spec ✅ Stable v2.0 ✅ Done
/tasks Generate concrete TDD tasks from design artifacts ✅ Stable v2.0 ✅ Done
/implement Execute tasks with TDD, anti-duplication checks ✅ Stable v2.0 ✅ Done
/validate Cross-artifact consistency analysis ✅ Stable - ⏳ Needs v2.0
/optimize Production readiness validation (perf, security, a11y) ✅ Stable v2.0 ✅ Done
/preview Manual UI/UX testing on local dev server ⚠️ Not shipped here - Compatibility shim only
/finalize Workflow completion, artifact archival, roadmap update ✅ Stable - ⏳ Needs v2.0
/debug Debug errors and update error-log.md ✅ Stable - ⏳ Needs v2.0

Read the full file on GitHub · 389 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 First seen · 389 lines · 0 tokens per session scan A ce75e4e7f262

Subscribe to this mod's changes

README is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,488 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.