agentmods.dev

build-epic

A controlled build cycle for completing one software epic, meaning a large feature or body of related work.

In plain words
What is it for?
It helps survey the task, plan work, create a feature branch, develop with TDD, verify behavior, audit code, draft a commit message, and release the branch. TDD means writing a failing test before the code that makes it pass.
Why use it?
It gives the feature a defined path from security review and planning through testing, code review, commit preparation, and release.

Skill for Claude CodeCodex

156 25d ago A scan 55 tokens original MIT
View the source file danielvm-git/bigpowers
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 skills/danielvm-git/bigpowers/build-epic
Any agent
npx skills add danielvm-git/bigpowers --skill build-epic
Clone the repo
git clone --depth 1 https://github.com/danielvm-git/bigpowers

Made for: Claude Code, Codex.

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,909 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.00055 $0.01909
Opus 5 $0.00028 $0.00955
Sonnet 5 $0.00011 $0.00382
Haiku 4.5 $0.00006 $0.00191

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

Security

Grade A, and why

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

.cline/skills/build-epic/SKILL.md · 106 lines

How it starts

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

story: e20s05

Build Epic

Scope: one story. Called by orchestrate-project Phase 4. Not a replacement for orchestrate-project.

Orchestrates the build flow for a single epic: survey → plan tasks → kickoff → TDD → verify → audit → commit → release.

HARD GATE — Set specs/state.yaml active_flow: build_epic and active_epic: eNN before starting.

HARD GATE — Not on main/master before step 3 (kickoff-branch).

Nine steps (epic_cycle in state.yaml)

Step Skill / action
0 security-review — threat-model epic scope → specs/security/epics/<id>/THREAT_MODEL.md
1 survey-context — confirm epic + story
2 plan-work — flesh out story tasks[] in specs/epics/eNN-slug/epic.yaml
3 kickoff-branch — feature branch + clean baseline
4 develop-tdd — red-green per task
5 verify-work — UAT + mechanical gates
6 audit-code — non-optional gate (pass/fail; fail → loop back to step 4)
7 commit-message — Conventional Commits draft
8 release-branch — PR or solo land (supports --squash-state)

Process

  1. Read specs/state.yaml, specs/execution-status.yaml, specs/release-plan.yaml, active specs/epics/eNN-slug/epic.yaml.
    • On story start (step 1): Write started_at ISO 8601 timestamp to execution-status.yaml under the story's key in the stories: section. The bp-timing.sh script already tracks skill-level timings — this is story-level.
  2. Step 0 — Threat Model: Run security-review against the epic's scope (read from the epic capsule). Output specs/security/epics/<epic-id>/THREAT_MODEL.md with surface area, vulnerability categories, risk level, and mitigation guidance.
  3. Assess Impact (Step 2): Before writing tasks, run assess-impact --lightweight on the proposed change. If the risk score exceeds 7, gate — require a grill-me session. Write the impact report to specs/IMPACT-<epic>-<story>.md. For net-new code with no existing dependents, skip.
  4. BCP Tracking (Step 2): After plan-work completes, read the bcps: count (Business Complexity Points story size) from the epic capsule and carry it into state.yaml as epic_cycle.story_bcps = N.
  5. BCP Plus (Step 2, optional): When the epic capsule carries a bcp_plus_breakdown (13-dimension sizing), also carry it into state.yaml as epic_cycle.bcp_plus. The breakdown maps each of the 13 dimensions to an integer count. NFR dimensions (11–13) that are N/A per the NFR Gate may be set to 0.
  6. If epic_cycle.step missing, set to 1.
  7. Run only the current step (resume mode) unless user asked for full auto-run.
  8. After step verify passes, increment epic_cycle.step in state.yaml (or bash scripts/bp-yaml-set.sh if available).
  9. On story complete, set execution-status.yaml story key to done; run bash scripts/sync-status-from-epics.sh.
    • On story complete (step 8): Write completed_at ISO 8601 timestamp to execution-status.yaml under the same story key. Format:

Read the full file on GitHub · 106 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 · 106 lines · 55 tokens per session scan A b360a1bbf924

Subscribe to this mod's changes

build-epic is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 55 tokens to every session and 1,909 once invoked, about $0.0003 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.

PlanningProject managementai-agentsautomationbmadclaude-codeclean-codecursor-rules
Related

Other skills, from other repositories

ponytail-debt

Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.

DietrichGebert/ponytail · 31 tokens

bmad-create-story

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".

LarsCowe/bmalph · 42 tokens

bmad-check-implementation-readiness

Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".

LarsCowe/bmalph · 32 tokens

bmad-create-epics-and-stories

Break requirements into epics and user stories. Use when the user says "create the epics and stories list".

LarsCowe/bmalph · 33 tokens

bmad-correct-course

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change".

LarsCowe/bmalph · 29 tokens

bmad-retrospective

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]".

LarsCowe/bmalph · 38 tokens