close-epic

Verifies an assembled epic against its PRD Definition of Done before closing it.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill close-epic-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-epic
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/close-epic
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill close-epic-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Per-slice tests prove each slice works in isolation, but nothing verifies that the assembled feature satisfies the PRD's epic-level Definition of Done. This Skill closes that gap with an adversarial integration and edge-case pass before an epic is allowed to ship. ## Core Features & Use Cases - Epic-level verification: Builds a rubric from the PRD (Definition of Done, goals, user stories, P0 requirements, NFRs, edge cases) and tests the assembled feature against it. - Two-scope adversarial pass: Hunts for failures both inward (integration seams between slices) and outward (blast-radius regressions in adjacent pre-existing code, mapped via /zoom-out). - Earned close-out: On pass, flips the PRD to Shipped, posts a closing comment, and closes the epic; on failure, posts an expected-vs-actual report and files full vertical-slice gap issues under the same PRD-ID. - Use Case: After grill -> to-prd -> to-issues -> /tdd completes all slices of PRD-042, run this Skill to confirm the whole feature works end-to-end and decide whether the epic can ship. ## Quick Start Run the close-epic skill on PRD-042 to verify the assembled epic against its Definition of Done and close it if it passes.

Frequently Asked Questions about close-epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an epic is ready to close after all slices pass?▼

Run the close-epic skill once every slice under the PRD is closed. It builds a rubric from the PRD's Definition of Done, user stories, and requirements, then runs an adversarial integration and edge-case pass on the assembled feature before closing the epic.

Why re-test an epic when all slice tests already pass?▼

Per-slice tests only prove each slice in isolation. Integration seams between slices, whole-system user stories, and regressions in adjacent pre-existing code are only visible once the feature is fully assembled, which is what this pass targets.

What happens when epic close-out verification finds gaps?▼

The epic stays open. The skill posts an expected-vs-actual report on the epic issue and files each code-testable gap as a full vertical-slice issue under the same PRD-ID, with the failing integration test as its acceptance criterion.

Can close-epic run while some slices are still open?▼

No. The skill checks that every slice tagged with the PRD-ID is closed first and stops if any remain open, since verifying a half-built epic produces noise rather than signal.

Does close-epic handle non-code-testable concerns like UX or performance?▼

Yes. Concerns that cannot be asserted in the test suite, such as UX judgment or performance under real load, are reported as findings in the expected-vs-actual report rather than being wrapped in unreliable tests.