agentmods.dev

build-epic

build-epic is a cursor rule for Cursor from danielvm-git/bigpowers. It costs 50 tokens per session (1,902 once invoked), scanned A, original, MIT.

A release workflow for completing one software epic, from planning and coding through testing, review, and release.

In plain words
What is it for?
Use it to coordinate a large feature or group of related tasks through branches, TDD, verification, code review, commits, and release preparation.
Why use it?
It gives a multi-step project task defined checkpoints, so important work is not skipped before release.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash scripts/decompose-conventions.sh.

not rated 267repo +6 27d ago A scan 50 tokens original MIT

Good fit Use it to coordinate a large feature or group of related tasks through branches, TDD, verification, code review, commits, and release preparation.

Compare 6 cursor rules from other repositories ↓
View source ↗ danielvm-git/bigpowers danielvm-git.github.io
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/danielvm-git/bigpowers
agentmods
npx agentmods add rules/danielvm-git/bigpowers/build-epic

Made for: Cursor.

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

README.md
[![agentmods](https://agentmods.dev/badge/rules/danielvm-git/bigpowers/build-epic/github.svg)](https://agentmods.dev/rules/danielvm-git/bigpowers/build-epic)
Your own site
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/build-epic"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/build-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 build-epic

Your own site · 80×15
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/build-epic"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/build-epic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,902 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.00050 $0.01902
Opus 5.5 $0.00020 $0.00761
Sonnet 5.5 $0.00010 $0.00380
Haiku 4.5 $0.00005 $0.00190

Measured 1mo ago against content hash 88a8f06e42fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.cursor/rules/build-epic.mdc · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 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 · 105 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 · 105 lines · 50 tokens per session scan A 88a8f06e42fb

Subscribe to this mod's changes

build-epic is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 50 tokens to every session and 1,902 once invoked, about $0.0002 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-09-03.

Claude CodePlanningProject managementai-agentsautomationbmadclean-codecursor-rules
Related

Other cursor rules, from other repositories

payload-cms

Payload CMS: collections, fields, hooks, access control, admin UI.

nedcodes-ok/cursorrules-collection · 734 tokens

monorepo

Monorepo: workspace references, shared packages, boundaries.

nedcodes-ok/cursorrules-collection · 476 tokens

pnpm

PNPM: workspace monorepos, efficient package management.

nedcodes-ok/cursorrules-collection · 365 tokens

ai-dev-os-ticket

Generates a ticket (local file or GitHub Issue) with implementation summary and checklist candidates derived from AI Dev OS guidelines. Used to create structured implementation tasks.

yunbow/ai-dev-os-plugin-cursor · 32 tokens

agent-workflow-orchestration

Mandatory PM-orchestrated subagent workflow — main agent is manager, no separate PM subagent.

95gabor/agentic-workflow · 949 tokens

12-new-project

Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.

orbitalsonic/AndroidPilot · 19 tokens