finish-epic

Close br epics after evidence-backed checks pass and append an Outcome.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill finish-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-epic
Source: https://github.com/sQVe/cape/tree/main/skills/finish-epic
Command: npx skills add https://github.com/sQVe/cape --skill finish-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined, evidence-based closure workflow for br epics, ensuring epics are only closed when every success criterion has verifiable evidence and an Outcome is appended for future traceability.

Core Features & Use Cases

  • Evidence-driven closure: validates each success criterion against concrete evidence (tests, lint results, hooks, and any manual verification steps) before closing the epic.
  • Outcome augmentation: appends a formal Outcome summary to the epic to document what shipped.
  • Safe governance: prevents premature closure and defers git operations to the user, maintaining an auditable closure process.

Quick Start

Run the closure workflow to verify an epic and finalize its closure.

Frequently Asked Questions about finish-epic

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

FAQPage Schema
How do I close an epic with evidence-based verification?

Closing an epic safely requires validating every success criterion against concrete evidence like tests, lint results, and manual checks. The workflow prevents premature closure by appending an Outcome summary and deferring git operations to the user.

What is evidence-driven epic closure in project management?

Evidence-driven epic closure is a governance workflow that validates each success criterion against concrete evidence like tests, lint results, and hooks before closing. It appends a formal Outcome summary to the epic to document what shipped for future traceability.

How do I prevent premature epic closure in development workflows?

Preventing premature epic closure requires a governance workflow that demands evidence for every success criterion before allowing closure. It validates tests, linting, and manual checks, deferring git operations to the user to maintain an auditable process.

Can I use automated verification and governance for epic closure?

Automated verification and governance for epic closure is supported by validating tests, lint results, and hooks against success criteria. The workflow requires evidence for each step and appends an Outcome before finalizing the closure.

Does epic closure require manual verification steps?

Epic closure can require manual verification steps alongside automated checks like tests and linting. The workflow validates all success criteria against concrete evidence, ensuring both automated and manual checks pass before appending an Outcome and closing the epic.