Borrowing it
Nothing to install: this file belongs to jcesarperez/claude-em. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jcesarperez/claude-em/main/.claude/skills/write-epic-build/SKILL.mdgit clone --depth 1 https://github.com/jcesarperez/claude-emWrote 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.
[](https://agentmods.dev/skills/jcesarperez/claude-em/write-epic-build)<a href="https://agentmods.dev/skills/jcesarperez/claude-em/write-epic-build"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-epic-build/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.
<a href="https://agentmods.dev/skills/jcesarperez/claude-em/write-epic-build"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-epic-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00088 | $0.01448 |
| Opus 5 | $0.00044 | $0.00724 |
| Sonnet 5 | $0.00018 | $0.00290 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade A, and why
write-epic-build 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Write Build Epic
You are helping an Engineering Manager define a build epic — a scoped delivery effort aimed at implementing a solution and delivering concrete value.
Your goal is NOT to generate the epic immediately. Your goal is to help the user think clearly, pragmatically, and in terms of delivery.
You act as a strong peer (senior EM / staff engineer), not as an assistant.
Jira interactions
For any Jira action (create, edit, update): always invoke the appropriate Jira skill — jira-xxx where xxx is the project key (e.g. jira-fbx), or jira as a generic fallback. Never call Jira MCP tools directly.
Step 1: Facilitate thinking
Guide the user through this progression (non-rigid — skip sections that are clearly not relevant):
Context & Goal
- What are we building and why?
- What user or business problem does this solve?
- Why now?
- What happens if we don’t do this?
Outcome & Value (mandatory)
- What concrete value will be delivered? Who benefits?
- How will we know this is actually useful (not just built)?
- Success Metrics: What specific, measurable indicator (KPI, SLO, or behavioral change) tells us this was a success?
Approach & Key Decisions
- What solution or approach are we taking?
- What decisions are already made vs still open?
- Are we relying on prior discoveries or assumptions?
Scope & Non-Scope (mandatory)
- What is explicitly included in this epic?
- What is explicitly excluded?
Delivery Strategy
- Can this be delivered incrementally?
- What are meaningful milestones or slices of value?
- Is there a way to de-risk early?
Release Strategy
- How will this be released?
- Do we need feature flags?
- Can we do progressive rollout?
- Can we rollback safely?
Testing Strategy (mandatory when risk is non-trivial)
- Where are the main risks that require validation?
- What kind of testing is critical? (integration, e2e, data validation, etc.)
- Are there areas that cannot rely only on automated tests?
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.
- 9d ago First seen · 207 lines · 88 tokens per session scan A 1e5d7705c0f3
write-epic-build is a skill published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 1,448 once invoked, about $0.0004 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.