agentmods.dev

epic-plan

A command that creates high-level plans for an Epic, meaning a large feature made up of several smaller deliverable slices.

In plain words
What is it for?
Use it after specification review to plan the boundaries, roadmap, integration points, and architecture decisions for a large feature.
Why use it?
It clarifies shared architecture, dependencies, risks, and rollout order before detailed tasks are written.

Command for Claude Code

58 +1 2mo ago A scan 22 tokens original MIT
View the source file loiane/specs-driven-development-spring-angular
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/loiane/specs-driven-development-spring-angular/epic-plan
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 453 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.00022 $0.00453
Opus 5 $0.00011 $0.00227
Sonnet 5 $0.00004 $0.00091
Haiku 4.5 $0.00002 $0.00045

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

Security

Grade A, and why

epic-plan 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/epic-plan.md · 44 lines

What it actually says

/epic-plan

Phase: 3a — Epic planning Owning agent: .claude/agents/spring-architect.md Skills used: epic-slicing-planning, spring-boot-4-conventions, openapi-contract-first, adr-authoring, performance-optimization

Purpose

Create high-level Epic planning artifacts before detailed slice-level tasks.

Inputs

  • <feature-id>.

Reads

  • .specs/<feature-id>/01-spec.md
  • .specs/<feature-id>/02-spec-review.md (verdict must be PASS)
  • .specs/_stack.json
  • .claude/templates/epic-design.template.md
  • .claude/templates/epic-roadmap.template.md

Writes

  • .specs/<feature-id>/03-epic-design.md
  • .specs/<feature-id>/03a-epic-roadmap.md
  • .specs/<feature-id>/adr/NNN-*.md (if needed)

Process

  1. Refuse if spec review is not PASS.
  2. Refuse if 01-spec.md has unresolved Q-NNN.
  3. Produce 03-epic-design.md: boundaries, shared architecture decisions, integration points, risks, and ADR links.
  4. Produce 03a-epic-roadmap.md: vertical slices, dependency order, milestone intent, and rollout strategy.
  5. Raise Q-NNN for any unresolved Epic-level decision and halt before detailed task decomposition.

Refuse if

  • 02-spec-review.md verdict is not PASS.
  • Any AC in 01-spec.md is unaccounted for in Epic design/roadmap.
  • Epic-level Q-NNN remains unresolved at handoff.

Done when

03-epic-design.md and 03a-epic-roadmap.md exist, are internally consistent, and the next recommended command is /plan.

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 · 44 lines · 22 tokens per session scan A 36c99975fda6

Subscribe to this mod's changes

epic-plan is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 453 once invoked, about $0.0001 per session on Opus 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.

Code reviewPlanningTestingangulargithub-copilotspec-driven-developmentspring-boot
Related

Other commands, from other repositories

spec-kitty-standalone

This host should read Spec Kitty's canonical standalone-invocation skill pack at.

Priivacy-ai/spec-kitty · 0 tokens

spec-kitty.analyze

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

Priivacy-ai/spec-kitty · 0 tokens

my-own-prompt

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

Priivacy-ai/spec-kitty · 0 tokens

sdd-featherspec-update

Check the installed FeatherSpec version and update safely — fetch a release, migrate, preserve customizations. Resumable.

GregorBiswanger/featherspec · 24 tokens

sdd-plan

Turn a spec into a persisted baby-step plan file — research, resume, impact analysis.

GregorBiswanger/featherspec · 18 tokens

sdd-specify

Adaptive product-owner interview that turns an idea into a lean, testable spec.

GregorBiswanger/featherspec · 16 tokens