skills.rest
humansys
humansysOFFICIAL
Explore all skills by this author →
WebsiteGitHub

rai-epic-close

Automate epic closure with retrospective generation, milestone tagging, and merge workflow.

71|8|Updated Feb 13, 2026
Search Tags:#automation#git#retrospective#release#governance#epic#merge-request
One-click install
npx skills add https://github.com/humansys/raise --skill rai-epic-close-humansys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rai-epic-close
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-epic-close
Command: npx skills add https://github.com/humansys/raise --skill rai-epic-close-humansys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close an epic with retrospective, push, and merge request to ensure governance and delivery.

Core Features & Use Cases

  • PRIME-driven steps: verify all stories are complete, generate a retrospective, tag the milestone, and coordinate a single epic merge workflow.
  • Governance enforcement: captures learnings, stores artifacts under work/epics path, and creates a single MR for the epic.
  • Use Case: closing E10 after all stories are done, ensuring release-ready documentation and metrics are captured.

Quick Start

Run the Epic Close workflow after all stories are complete to finalize governance, tagging, and delivery.

Frequently Asked Questions about rai-epic-close

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

FAQPage Schema
How do I automate epic closure with a retrospective and merge request?▼

Automate epic closure by generating a retrospective, tagging the milestone, and coordinating a single merge workflow. The process verifies all stories are complete and executes governance steps to finalize delivery.

What is the process for finalizing epic governance after all stories are complete?▼

Epic governance finalization involves verifying story completion, generating a retrospective document, tagging a git milestone, and creating a single merge request across the epic lifecycle.

How do I generate a release-ready retrospective document for a completed epic?▼

Generate a retrospective document by consuming inputs from the epic scope and all individual story retrospectives. The output captures learnings and metrics for release-ready documentation.

Do I need a manifest configuration to identify the development branch for epic merge workflows?▼

Yes, the epic merge workflow uses manifest configuration to identify the development branch. This ensures the single merge request targets the correct branch during governance execution.

Can I tag a git milestone and create a merge request at the same time during epic closure?▼

Yes, the epic closure workflow coordinates both milestone tagging and merge request creation simultaneously. It executes these governance steps together once all stories are merged.

What are the limitations of automating epic closure with this workflow?▼

The workflow is applicable only when all stories are complete and merged. It cannot execute governance steps or generate retrospectives for epics that still have open or unmerged stories.

Related Skills

Explore More Software Engineering Skills→
ImaginerLabsImaginerLabs

bmad-retrospective

Facilitate post-epic retrospectives to extract lessons and generate actionable items.

Official
Advanced
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
projectbluefinprojectbluefin
134

finishing-a-development-branch

Verify tests and present integration options for completing a Git branch.

Official
Advanced
virtenginevirtengine
17

complete-milestone

Archive milestone docs, update governance files, and tag releases in Git.

Official
Advanced