epic-review SKILL.md skillA
epic-review from ehnruiz/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ehnruiz/claude-skills/epic-review@git:20261015.dd12a4bPins git:20261015.dd12a4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ehnruiz/claude-skills
- Path
skills/epic-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261015.dd12a4b, committed Oct 15, 2026
- Size
- 7,082 bytes
- Repository stars
- 3
- License
- MIT
Review a Jira epic (or the Jira Product Discovery idea it implements) against its own In Scope list - which items are done, partly done, not started, or have no evidence - then flag scope conflicts and stale statuses, and draft the In Scope list for the follow-on epic. Use this whenever the user is preparing for an epic review, quarter close-out, scope or refinement meeting, asks "what was completed on this epic", "what is left for Q2", "what should carry over…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Epic review Answer the question a quarter-close meeting asks: of what this epic promised, what is done, what is left, and what goes into the next one. The answer comes from ticket evidence, item by item, not from the epic's status field, which is usually stale. **Requires:** the Atlassian MCP connector (`getJiraIssue`, `searchJiraIssuesUsingJql`, `searchConfluence`, and `listJiraIssueComments` through `executeRead`). Read-only by default. Companion skills: `ticket-write` files any missing work this review uncovers, `ticket-digest` recaps it. ## Team defaults The rules below are team-neutral. These values are examples. Read the real ones from the user's `CLAUDE.md` or from the epic itself, and ask once when neither says: | Setting | Example | | --- | --- | | Jira site / delivery project | `your-site.atlassian.net`, project `PROJ` | | Discovery (JPD) project | `DISC`; ideas link to delivery epics with the **Polaris work item link** type (`implements` / `is implemented by`) | | Epic summary shape | `T1 \| Q1FY27 \| Area \| Name (Phase n - ...)`; the next quarter's epic is usually a clone, linked with the **Cloners** type | …
Read the whole file at its exact version.
How to install
mdr add ehnruiz/claude-skills/epic-review@sha256:bfa232991e024b0eThe line at the top of this page pins the label git:20261015.dd12a4b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_encasg6vm2fzmb2h)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 15, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7082 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ehnruiz/claude-skills · 3 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_encasg6vm2fzmb2h GET https://markdownregistry.com/api/v1/resolve?ref=ehnruiz/claude-skills/epic-review GET https://markdownregistry.com/api/v1/blob/bfa232991e024b0ea0479389723f6587e5ff20bc9ea498936f1226d4989b9422
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ehnruiz/claude-skills
Every file in ehnruiz/claude-skills