epic-close

Automate epic closure by coordinating refinement, validation, and promotion to main.

4|3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/steilerDev/cornerstone --skill epic-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-close
Source: https://github.com/steilerDev/cornerstone/tree/main/.claude/skills/epic-close
Command: npx skills add https://github.com/steilerDev/cornerstone --skill epic-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close and consolidate an epic after all stories are merged to beta by coordinating refinement, E2E validation, UAT, documentation, and promotion to main, reducing risk and manual overhead.

Core Features & Use Cases

  • Task creation and tracking across refinement, E2E validation, UAT, and release
  • Rebase onto origin/beta, verify all stories are merged, and perform health checks
  • Collect refinement items and generate refinement PRs for implementation teams
  • E2E validation and UAT workflows, with documentation and promotion to main
  • Dynamic handling of fix rounds (e.g., UAT/E2E fix rounds) and recovery if progress is interrupted
  • Delegation to /release with epic context to build enriched promotion PRs and gate checks

Quick Start

Provide the epic issue number to initiate the closing workflow.

Frequently Asked Questions about epic-close

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

FAQPage Schema
How do I automate epic closure and promotion from beta to main?

Automate epic closure by providing an epic issue number to trigger a workflow that coordinates refinement, E2E validation, UAT, documentation, and promotion to main. This reduces manual overhead and ensures consistent release orchestration.

What is the process for coordinating E2E validation and UAT during an epic release?

Coordinating E2E validation and UAT during an epic release involves task creation and tracking across teams, performing health checks after rebasing onto origin/beta, and executing dynamic fix rounds. The workflow enforces guardrails and handles recovery if interrupted.

Can I handle fix rounds dynamically when closing an epic with failed validation?

Yes, you can handle fix rounds dynamically when closing an epic. The workflow supports dynamic iterations for UAT and E2E fix rounds, enforcing guardrails and providing recovery mechanisms if progress is interrupted during validation.

How do I generate refinement PRs for implementation teams before promoting an epic?

Generate refinement PRs by collecting refinement items after verifying all stories are merged to beta. The workflow collects these items and creates pull requests for implementation teams to address before final promotion.

Does epic closure require all stories to be merged to beta before starting?

Yes, epic closure requires all stories to be merged to beta. The workflow rebases onto origin/beta, verifies all stories are merged, and performs health checks before proceeding with validation and promotion steps.

What's the best way to orchestrate multi-team release promotion for an epic?

Orchestrate multi-team release promotion by delegating to the release workflow with epic context to build enriched promotion PRs and gate checks. This ensures consistent promotion to main with proper documentation and validation.