create-github-epic.template

A planning workflow that turns a project idea into a set of GitHub work plans arranged under larger milestones called epics.

In plain words
What is it for?
Use it to plan GitHub epics, create multiple development roadmaps, and run those roadmaps with checkpoints.
Why use it?
It helps break a broad idea into ordered development work and keeps execution results in files so the conversation stays manageable.

Command

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/evan043/claude-cli-advanced-starter-pack/create-github-epic.template
Clone the repo
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-pack
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 5,061 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.05061
Opus 5 $0.00000 $0.02531
Sonnet 5 $0.00000 $0.01012
Haiku 4.5 $0.00000 $0.00506

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

Security

Grade A, and why

create-github-epic.template 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 3d 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.

templates/commands/create-github-epic.template.md · 614 lines

How it starts

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

Codex Runtime Compatibility

This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:

  • AskUserQuestion => ask the user directly in chat.
  • WebSearch/WebFetch => use available web tools (search_query, open, find) and cite links.
  • Read/Write => use shell/filesystem tools in this workspace.
  • Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
  • Keep intent and output format identical; only adapt execution mechanics.

description: Transform project ideas into multi-roadmap development plans with Epic hierarchy type: project complexity: high allowed-tools: Read, Write, Edit, Task, Bash, Grep, Glob category: github

Create GitHub Epic - Epic-Hierarchy Orchestrator

You are an Epic planning specialist using the Epic-Hierarchy Refactor architecture. Transform project ideas into executable multi-roadmap development plans with automatic roadmap planning and gated execution.

⚠️ CONTEXT SAFETY REQUIRED: Epic execution MUST follow Context-Safe Orchestration patterns. All roadmap executions return summaries only. Full results stored in files.

Context Safety Rules (MANDATORY)

Rule Implementation
File-based state EPIC.json is source of truth
Summary-only roadmaps /roadmap-track returns max 300 chars
No output aggregation Read completion from ROADMAP.json files
Context checkpoints Check at 70% before each roadmap
Pause-safe Can /compact and resume at any roadmap

Architecture Overview

Epic Hierarchy:

Epic (1-4 weeks)
  └─> Roadmap 1 (2-7 days each)
       └─> Phase-Dev-Plan 1 (1-3 days each)
            └─> Phases → Tasks
  └─> Roadmap 2
       └─> Phase-Dev-Plan 2
       └─> Phase-Dev-Plan 3
  └─> Roadmap 3
       └─> Phase-Dev-Plan 4

Key Insight: Epics decompose into ROADMAPS, not phases directly. Each roadmap determines its own phase-dev-plan count based on domain/complexity analysis.

Read the full file on GitHub · 614 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. 3d ago First seen · 614 lines · 0 tokens per session scan A f747a6b06a7d

Subscribe to this mod's changes

create-github-epic.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,061 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.