close-out-epic SKILL.md skillA
close-out-epic from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/close-out-epic@git:20261027.599bb58Pins git:20261027.599bb58 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/close-out-epic/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261027.599bb58, committed Oct 27, 2026
- First version recorded
- Oct 26, 2026
- Size
- 11,571 bytes
- Repository stars
- 30
- License
- MIT
Close out an epic before it's released, so that its open-ticket count means something. Lists every open ticket under the epic and proposes, for each, fix before release, move to the epic's follow-up epic, or make standalone, then waits for the user's decisions. Moves the deferred tickets out of the epic with a link back, rewrites each one's description so it still makes sense outside the epic, posts one closing comment on the epic saying what was deferred and where it went, and checks the epic…
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
# Close Out Epic An epic released with tickets still open under it can mean two very different things: "we shipped and left work behind" or "we decided this was ready". Closing it out makes it the second one, on the record. Every ticket still under the epic at release is either done or being done before release; everything else has been moved somewhere it will be found, with a trail back. **First, load the team config with `roost-config`.** Do this at release time, not earlier. Until then, "later" items stay in the epic (`slice-handoff` tracks them in its Carry-over comment), because decisions can change. ## Inputs - **EPIC:** the epic's ticket key. ## 1. List what's open Find every open ticket under EPIC, at any depth: its children of every type, and their sub-tasks. "Open" means it isn't closed (done, won't do, or any other closed state) and it isn't at `tracker.statuses.ready_for_release` (the tracker adapter's common searches show the query). Read the epic's **Carry-over** comment too, if it has one. Leave out the epic's deploy ticket and its sub-tasks: they're the release itself. Leave out the tests' shared setup, where it's a ticket (the tests adapter's "Shared… …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/close-out-epic@sha256:fd668ce05bf0c950The line at the top of this page pins the label git:20261027.599bb58, 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_rpnk5ag544dnohaj)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 26, 2026 and Oct 27, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.599bb58 latest | 2026-10-27 | 599bb58 | 11,571 B | A | view · diff |
| git:20261027.47c5175 | 2026-10-27 | 47c5175 | 10,997 B | A | view · diff |
| git:20261027.e9b7c4f | 2026-10-27 | e9b7c4f | 10,016 B | A | view · diff |
| git:20261026.505a1da | 2026-10-26 | 505a1da | 8,974 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 8,990 B | A | view |
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 (11571 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rpnk5ag544dnohaj GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/close-out-epic GET https://markdownregistry.com/api/v1/blob/fd668ce05bf0c95089e63edce9fe488cb010157ead4deeeee4c329986f5a694f
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.