A command for managing feature development from a written specification through deployment, using separate workflow stages and quality checks.

Use it to start or continue feature work, manage epics and sprints, track workflow state, and run development phases through deployment.

It gives complex feature work a saved, resumable process with visible progress instead of relying on one uninterrupted session.

feature — Command for Claude Code by marcusgoll/Spec-Flow

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/marcusgoll/Spec-Flow

agentmods

npx agentmods add commands/marcusgoll/spec-flow/feature

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/marcusgoll/spec-flow/feature/github.svg)](https://agentmods.dev/commands/marcusgoll/spec-flow/feature)

Your own site

<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/feature"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/feature/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/feature"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/feature.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 7,718 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.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.07718
Opus 5.5	$0.00005	$0.03087
Sonnet 5.5	$0.00003	$0.01544
Haiku 4.5	$0.00001	$0.00772

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

Security

Grade A, and why

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

.claude/commands/core/feature.md · 925 lines

How it starts

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

CRITICAL ARCHITECTURE (v5.0 - Domain Memory v2):

This orchestrator is ultra-lightweight. You MUST:

Read state from disk (state.yaml, interaction-state.yaml, domain-memory.yaml)
Spawn isolated phase agents via Task tool - NEVER execute phases inline
Handle user Q&A when agents return questions
Update state.yaml after each phase
NEVER carry implementation details in your context

Benefits: Unlimited feature complexity, observable progress, resumable at any point, each phase gets fresh context.

Git status: !git status --short

Current branch: !git branch --show-current

Recent features: !ls -t specs/ 2>/dev/null | head -5

Active workflow state (if any): !find specs -name "state.yaml" -exec grep -l "status: in_progress\|status: failed" {} \; 2>/dev/null | head -3

Deployment model detection: !git branch -r | grep -q "staging" && echo "staging-prod" || (git remote -v | grep -q "origin" && echo "direct-prod" || echo "local-only")

Worktree context: !bash .spec-flow/scripts/bash/worktree-context.sh info 2>/dev/null || echo '{"is_worktree": false}'

Studio context (multi-agent isolation): !bash .spec-flow/scripts/bash/worktree-context.sh studio-detect 2>/dev/null || echo ""

Worktree preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "worktrees.auto_create" --default "true" 2>/dev/null || echo "true"

Planning depth preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "planning.auto_deep_mode" --default "false" 2>/dev/null || echo "false"

Auto-ship preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "deployment.auto_ship" --default "false" 2>/dev/null || echo "false"

Auto-merge preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "deployment.auto_merge" --default "false" 2>/dev/null || echo "false"

Auto-finalize preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "deployment.auto_finalize" --default "true" 2>/dev/null || echo "true"

<planning_depth>

Planning Depth Mode (--deep / --auto)

Flags in $ARGUMENTS:

--deep → Force ultrathink/craftsman planning for this feature
--auto → Use preferences to determine depth (respects auto_deep_mode), AND continue through ship→finalize without stopping
Neither → Interactive mode, respects preference triggers

Pass flag to /plan phase: When spawning the plan-phase-agent, include the planning mode:

If --deep in arguments: Pass --deep to /plan
If --auto in arguments: Determine from preferences and pass appropriate flag
Store planning_mode in state.yaml for reference

State tracking:

# In state.yaml
planning:
  mode: deep  # or standard
  ultrathink_enabled: true
  craftsman_decision_generated: true

</planning_depth>

<auto_mode>

Read the full file on GitHub · 925 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.

1mo ago First seen · 925 lines · 13 tokens per session scan A 27ac4b54911a

Subscribe to this mod's changes

feature is a command published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 24d ago), licensed MIT. It adds 13 tokens to every session and 7,718 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-30.

DevOps and cloud Planning ai-agents ai-assisted-development ai-workflows automation bash claude

feature

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Planning Depth Mode (--deep / --auto)

What this file has done since we first saw it

Other commands, from other repositories

sync-linear

task-verify

milestone-list

amp-register

amp-identity

example