skills.rest
fcastrillo
fcastrilloCOMMUNITY
Explore all skills by this author →
GitHub

rai-epic-close

Closes a project epic by finalizing gradebook entries, aggregating statistics, and reopening the next epic.

Updated Feb 4, 2026
Search Tags:#retrospective#backlog#telemetry#branch-cleanup#epic-close#git-merge
One-click install
npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-epic-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rai-epic-close
Source: https://github.com/fcastrillo/carbtrack-ai/tree/main/.claude/skills/rai-epic-close
Command: npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-epic-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This process closes an epic by coordinating retrospective, metrics capture, branch cleanup, and a merge into development to formalize completion.

Core Features & Use Cases

  • End-to-end epic closure: conduct retrospective, capture metrics, delete story and epic branches, update backlog, and emit telemetry.
  • Enforce governance: ensure prerequisites are met (all stories complete, tests passing) before merging, preserving history for continuous improvement.
  • Prepare for the next cycle: update local context and prepare the next epic.

Quick Start

Close the current epic by running the full close workflow after all stories are complete.

Frequently Asked Questions about rai-epic-close

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

FAQPage Schema
How do I close an epic with a retrospective and git merge?▼

To close an epic, you run a workflow that coordinates retrospective creation, metrics capture, branch cleanup, and a merge into development to formalize completion. This enforces prerequisites like passing tests before merging.

What steps are required to perform an epic closure and branch cleanup?▼

Epic closure requires conducting a retrospective, capturing metrics, deleting story and epic branches, updating the backlog, and emitting telemetry. It enforces end-to-end steps to ensure all stories are complete and tests pass before merging.

When do I need to run an epic close workflow?▼

You need an epic close workflow when all stories within an epic are complete, the epic branch has been merged, tests pass, and the backlog is updated. It formalizes completion and prepares the context for the next cycle.

Can I merge to development if some stories in the epic are still incomplete?▼

No, merging to development through this workflow requires all stories to be complete and tests to pass. The process enforces these prerequisites to preserve history for continuous improvement and proper governance.

Does epic closure include backlog updates and telemetry emission?▼

Yes, epic closure includes updating the backlog and emitting telemetry alongside retrospective creation and branch deletion. These steps ensure local context is updated and metrics are captured for continuous improvement.

Why does branch cleanup matter when closing an epic?▼

Branch cleanup matters during epic closure because it involves deleting story and epic branches after merging to development. This enforces governance, preserves history, and prepares the environment for the next epic cycle.

Related Skills

Explore More Product & Management Skills→
humansyshumansys
71

rai-epic-close

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

Official
Advanced
ElliotJLTElliotJLT
60

retrospective

Document post-task reflections with sections for failed attempts, what worked, and learnings.

Community
Basic
humansyshumansys
71

rai-story-close

Merge a story feature branch into the development branch and update epic tracking.

Official
Advanced
sQVesQVe

finish-epic

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

Community
Advanced