# Epic Resolution

> Closeout protocol for parent epics — answers "we resolved all epic subs, are we done now?" with a structured matrix + verdict recommendation (close / keep open / create missing subs / retire-supersede). Sibling to epic-review (which handles entry); this is the exit gate. Triggers: Use this skill when the last required sub of an epic closes, when a team member claims an epic is complete or substrate-side complete, before closing an epic as COMPLETED, or when a peer broadcasts an epic-readiness signal that needs reconciliation against parent ACs.

- Skill: `neomjs/epic-resolution` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add neomjs/epic-resolution`
- Raw SKILL.md: https://api.skillmd.com/api/skills/neomjs/epic-resolution/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: neomjs (https://skillmd.com/u/neomjs)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/neomjs/epic-resolution

---

# Epic Resolution
If you are about to declare an epic complete, close an epic, propose creating new subs to complete one, or react to a peer broadcast that an epic is "ready for handoff" / "components look solid", you MUST immediately use the `view_file` tool to read and strictly adhere to `.agents/skills/epic-resolution/references/epic-resolution-workflow.md` before posting any verdict or recommendation.

