implement-epic

implement-epic is a command for Claude Code from marcusgoll/Spec-Flow. It costs 19 tokens per session (2,326 once invoked), scanned A, original, MIT.

A command for carrying out several planned development sprints according to their dependencies. A sprint is a defined piece of project work, and dependencies are tasks that must happen first.

In plain words
What is it for?
It validates an epic and its sprint plan, groups work into dependency layers, and sends independent feature tasks for implementation.
Why use it?
It removes the need to manually sequence related work and can run independent sprints at the same time.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash .spec-flow/scripts/bash/sprint-utils.sh validate "$EPIC_DIR".

Good fit It validates an epic and its sprint plan, groups work into dependency layers, and sends independent feature tasks for implementation.

Compare 6 commands from other repositories ↓
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/implement-epic

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 implement-epic

README.md
[![agentmods](https://agentmods.dev/badge/commands/marcusgoll/spec-flow/implement-epic/github.svg)](https://agentmods.dev/commands/marcusgoll/spec-flow/implement-epic)
Your own site
<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/implement-epic"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/implement-epic/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 implement-epic

Your own site · 80×15
<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/implement-epic"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/implement-epic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,326 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.02326
Opus 5.5 $0.00008 $0.00930
Sonnet 5.5 $0.00004 $0.00465
Haiku 4.5 $0.00002 $0.00233

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

Security

Grade A, and why

implement-epic 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/implement-epic.md · 315 lines

How it starts

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

/implement-epic - Parallel Sprint Execution

Workflow position: epic → plan → tasks → implement-epic → optimize → ship

Key principles:

  • Layers execute sequentially (dependencies respected)
  • Sprints within a layer run in parallel (single message, multiple Task calls)
  • Workers implement one feature at a time (Domain Memory pattern)
  • Errors classified and handled via error-recovery skill

Epic Directory: !ls -td epics/[0-9]*-* 2>/dev/null | head -1

Sprint Plan: !cat epics/*/sprint-plan.md 2>/dev/null | head -30

Sprint Count: !grep -c "^## Sprint S" epics/*/sprint-plan.md 2>/dev/null || echo "0"

Execution Layers: !bash .spec-flow/scripts/bash/sprint-utils.sh layers "$(ls -td epics/[0-9]*-* 2>/dev/null | head -1)" 2>/dev/null

Auto Mode: !echo "$ARGUMENTS" | grep -q "\-\-auto-mode" && echo "enabled" || echo "disabled"

Step 1: Validate Prerequisites

EPIC_DIR=$(ls -td epics/[0-9]*-* 2>/dev/null | head -1)

if [ -z "$EPIC_DIR" ]; then
    echo "ERROR: No epic directory found"
    echo "Run /epic first to create an epic"
    exit 1
fi

# Validate sprint directories exist
bash .spec-flow/scripts/bash/sprint-utils.sh validate "$EPIC_DIR"

Read sprint-plan.md to understand execution layers:

cat "$EPIC_DIR/sprint-plan.md"

Step 2: Initialize Domain Memory (If Missing)

For each sprint without domain-memory.yaml, initialize it:

for sprint_dir in "$EPIC_DIR/sprints"/*/; do
    if [ ! -f "${sprint_dir}/domain-memory.yaml" ]; then
        SPRINT_ID=$(basename "$sprint_dir")
        echo "Initializing domain memory for $SPRINT_ID..."

        # Use initializer agent
        Task(subagent_type="initializer", prompt="
            Initialize domain memory for sprint.
            Sprint directory: ${sprint_dir}
            Tasks file: ${sprint_dir}/tasks.md
            Workflow type: epic-sprint
        ")
    fi
done

Read the full file on GitHub · 315 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 · 315 lines · 19 tokens per session scan A 0474a8bbf004

Subscribe to this mod's changes

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