close-epic

name	close-epic
description	Formal epic closure ritual — security audit, CHANGELOG consolidation, tagging, merge
version	2.0.0
compat	claude-code, codex, cursor, openclaw

Skill: Close Epic (Consolidation and Versioning Ritual)

Purpose

Govern the formal completion of a strategic development block (Epic). Coordinates the macro security audit, version freezing via Git tags, and institutional knowledge preservation in the repository.

---

The 7 Ritual Steps (Unalterable Sequential Order)

Step 1: Macro Security Audit

• Action: Mandatorily invoke the @security-audit sub-skill. All new endpoints and changes from the Epic are deeply scanned.
• Block: If there are isolation failures, potential data leaks, or missing security tokens, the closure is immediately canceled.

Step 2: Definitive CHANGELOG Consolidation

• Action: Move all accumulated bullet points from [Unreleased] into a new official semver version with the current system date.
• Format: ## [MAJOR.MINOR.PATCH] — YYYY-MM-DD · E[N] · [Epic Name]

Step 3: History Update in AGENT_TASKS.md

• Action: Mark the complete Epic with the ✅ emoji. Record the closure date, merge commit hash or ID, generated tags, and a "Lessons Learned" block.

Step 4: Documentation-Only Commit

• Action: Make a commit containing only modifications to control documentation (CHANGELOG.md and AGENT_TASKS.md).
• Message: docs: close E[N] formally in control logs

Step 5: Clean Integration via --no-ff Merge

• Action: Switch to the main branch (main), pull remote changes, and merge the epic branch forcing a merge commit.
• Commands:

  git checkout main
  git pull origin main
  git merge --no-ff epic/e[N]-[name] -m "merge: merge epic E[N] - [Name]"
  git push origin main
  

Why: The --no-ff (no-fast-forward) flag preserves the branch structure in Git's historical graph, visually isolating the Epic's lifecycle.

Step 6: Permanent Tag Generation (Restoration Point)

• Action: Create an annotated Git tag to mark the stable project deliverable.
• Commands:

  git tag -a E[N]-complete -m "Stable release of Epic [N]"
  git push origin --tags
  

Step 7: Final Executive Report

• Action: Present an on-screen summary showing: total closed tasks, secured endpoints, assigned version, and an explicit reminder for the human developer to replicate these notes if they use external planning tools (like Claude.ai Projects).

---

Golden Infrastructure Rule

⚠️ NO AUTO-DELETE OF BRANCHES: Epic and Task branches (local and remote) must not be destructively deleted post-merge. They are intentionally preserved as part of the repository's technical and pedagogical memory.