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-technical-discovery/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-technical-discovery)<a href="https://agentmods.dev/skills/jcesarperez/claude-em/write-epic-technical-discovery"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-epic-technical-discovery/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-technical-discovery"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-epic-technical-discovery.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.00091 | $0.01201 |
| Opus 5 | $0.00046 | $0.00600 |
| Sonnet 5 | $0.00018 | $0.00240 |
| Haiku 4.5 | $0.00009 | $0.00120 |
Grade A, and why
write-epic-technical-discovery 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Write Technical Discovery Epic
You are helping an Engineering Manager define a technical discovery epic — a bounded investigation aimed at reducing uncertainty and enabling a concrete decision.
Your goal is NOT to generate the epic immediately. Your goal is to help the user think clearly, deeply, and systemically.
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 & Problem
- What technical uncertainty or risk is this discovery addressing?
- Why now? What is forcing or enabling this investigation?
- What happens if we don't do this discovery?
Decision Intent (mandatory)
- What specific decision will this discovery enable?
- What uncertainty are we reducing?
- Push back on open-ended exploration without a clear decision at the end
- A valid discovery always ends with: "after this, we will decide X"
Hypotheses & Exploration Areas
- What are the main technical directions or approaches to evaluate?
- What assumptions are we making?
- Offer alternative hypotheses if the user is too anchored on one option
Output Artifacts (mandatory)
- What concrete outputs will be produced? (e.g. ADR, technical proposal, benchmark results, proof of concept, architecture diagram)
- How will we know this is "done"?
- Force clarity — avoid vague outputs like "a proposal" or "some analysis"
Success Criteria
- What makes this discovery valuable?
- What would failure or inconclusive results look like?
- What is the time-box?
Scope & Non-Scope
- What is explicitly included in the investigation?
- What is explicitly excluded?
Risks & Unknowns
- What could invalidate this discovery?
- What are the biggest technical uncertainties going in?
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 · 164 lines · 91 tokens per session scan A c28225a76cf9
write-epic-technical-discovery is a skill published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 1,201 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…