close-out-epic
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 has no open tickets left. Run it again after the release ships, to confirm production runs it, check each release workflow and its tracker sync, close any ticket left waiting to ship with the version it shipped in, rewrite the epic's Release order and Close-out comments as shipped, and offer to draft the epic's release notes. Use when the user says "close out PROJ-X", "get PROJ-X ready to release", "move the leftovers out of the epic", "what's still open in this epic", "wrap up the epic" or "the
Beakpoint-Insights · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Beakpoint-Insights/roost --skill close-out-epicAbout this skill
name: close-out-epic description: 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 has no open tickets left. Run it again after the release ships, to confirm production runs it, check each release workflow and its tracker sync, close any ticket left waiting to ship with the version it shipped in, rewrite the epic's Release order and Close-out comments as shipped, and offer to draft the epic's release notes. Use when the user says "close out PROJ-X", "get PROJ-X ready to release", "move the leftovers out of the epic", "what's still open in this epic", "wrap up the epic" or "the epic shipped", and from build-epic right before release QA.
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 setup"): it's part of the epic's tests, and closes with the last test that uses it; close any whose tests are all done. Leave out person-owned tasks (labelled tracker.person_task_label) and manual tests whose description says When: after release ("Manual tests" in the tests adapter) too: they stay in the epic with their owner. List the ones not done yet in the Close-out comment, with their owner and "When".
For each ticket, note what it's about (from its summary, description and links), where it came from (story, review finding, exploratory testing), and its Components.
2. Propose a place for each
| Place | When |
|---|---|
| Before release | It harms a customer at launch: security, data loss, a broken main flow, a 5xx on a public endpoint, or an accessibility failure in a main flow. It stays in the epic and gets fixed. |
| Follow-up epic | It's still about this epic's feature, and it's the kind of work you'd plan together with the rest of the feature's leftovers (hardening, edge cases, polish of the same screens and endpoints). |
| Standalone | It came up during the work but isn't about the feature: shared infrastructure, logging, tooling, lint, local development. It belongs with general engineering work. |
Judge each the triage-ticket way: is it real, who does it hurt, how badly. Show one table, with a recommendation and a one-line reason each:
| # | Ticket | Recommendation | Why |
|---|---|---|---|
| 1 | PROJ-2814 Onboarding loses focus on a 400 | Before release | Accessibility failure in sign-up, the epic's main flow |
| 2 | PROJ-2813 Page through more than 100 keys | Follow-up epic | API keys feature; no customer near 100 keys at launch |
| 3 | PROJ-2828 Fix the 44 lint errors | Standalone | Not about the feature |
This is the only stop. Wait for the user's decisions, then carry them all out without asking again. If any ticket is "before release", say the close-out finishes when those are done, and come back to step 5 then.
3. Make each moved ticket stand on its own
A ticket written inside an epic leans on things that only make sense there: review finding codes ("U9", "A5"), "the checkpoint", plan contracts ("C3"), slice names, and branch names that disappear once merged. Before moving a ticket, read its description and add a short Background paragraph at the top:
- which epic and feature it came from (with the epic's key), and what that epic shipped that this builds on;
- the code it's about now: file paths on
main(or the merged stack), not branch names or PR numbers that will be closed; - any shorthand replaced with plain words.
Keep the rest of the description as it is. If the description already stands on its own, add only the first line ("Came from PROJ-X, …").
4. Move them
- Follow-up epic: if any ticket goes there, create the follow-up epic once (reuse it if EPIC already has one): summary "<EPIC's summary>: follow-ups", the same Components as the tickets, a description that says it holds work deferred from EPIC at release, and a "relates to" link to EPIC. Set each ticket's parent to it.
- Standalone: remove the parent.
- Every moved ticket gets a "relates to" link to EPIC, in addition to the links it already has (the story it came from).
Set and clear parents as the tracker adapter says ("Set or clear a parent"). Read every ticket back afterwards: parent, links and description.
5. Close the epic out
- Keep one Close-out comment on EPIC, starting with the heading "Close-out": what shipped (the stories), and what was deferred, as a table of ticket, where it went (follow-up epic key, or standalone), and why. Link the follow-up epic. The first run creates it