aiwfx-wrap-epic

Closes an aiwf epic by verifying milestones, scaffolding a wrap artefact, and merging the epic branch with trailered commits.

Updated May 9, 2026
One-click install
npx skills add https://github.com/23min/aiwf --skill aiwfx-wrap-epic-23min
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwfx-wrap-epic
Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded-rituals/plugins/aiwf-extensions/skills/aiwfx-wrap-epic
Command: npx skills add https://github.com/23min/aiwf --skill aiwfx-wrap-epic-23min

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing a long-running epic in an aiwf-tracked project involves many error-prone steps: verifying every milestone is done, harvesting decisions into ADRs, updating the changelog, promoting the epic status, and merging the integration branch with correct provenance trailers. Doing this by hand risks untrailered merge commits, stale changelogs, ended authorization scopes, and unvalidated merges reaching mainline. ## Core Features & Use Cases - Precondition verification: Confirms all milestones are done, the working tree is clean, the local CI gate is green after reconciling with mainline, and no claimed-closed gaps remain open. - Wrap artefact scaffolding: Creates wrap.md capturing delivered milestones, a changelog entry composed from milestone release notes, ratified ADRs, decisions, and follow-up gaps. - Declared-sequence gate: Executes the terminal local sequence (wrap-artefact commit, promote-to-done, roadmap regen, trailered merge) under one explicit human approval gate, with push and branch deletions as separate gates. - Use Case: After the final milestone of epic E-0012 merges, ask the assistant to wrap the epic; it verifies preconditions, drafts the wrap artefact and changelog entry, runs a scoped doc-lint, and drives the gated commit-and-merge sequence. ## Quick Start Ask the assistant to wrap epic E-NNNN once every milestone in it shows status done, and approve the declared sequence of commits it presents.

Frequently Asked Questions about aiwfx-wrap-epic

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

FAQPage Schema
How do I close an epic in aiwf after all milestones are done?

Invoke the wrap-epic workflow once every milestone shows status done. It verifies preconditions with aiwf check, scaffolds a wrap.md artefact, promotes the epic to done, regenerates the roadmap, and merges the epic branch into mainline with a trailered merge commit.

What git trailers does an aiwf epic wrap commit require?

The wrap-artefact commit and the merge commit must carry three exact trailers: aiwf-verb: wrap-epic, aiwf-entity: E-NNNN, and aiwf-actor: human/<id> resolved from git config user.email. Missing or mis-cased trailers trigger the kernel's provenance-untrailered-entity-commit finding.

Why must aiwf promote run before the merge when wrapping an epic?

The promote commit ends the authorize scope opened when the epic started, so it must be the last verb-driven commit; later verb-routed commits would carry an ended-scope aiwf-authorized-by trailer and fail provenance-authorization-ended on push. Merging before the promote leaves mainline carrying the merge without the status flip.

Can I wrap an aiwf epic while a milestone is still in progress?

No. Every milestone in the epic must have status done, confirmed via aiwf check, before wrapping begins. If any milestone is still in_progress or draft, the workflow stops and reports them rather than improvising around an unfinished epic.

Does wrapping an aiwf epic delete branches or cut a release?

Local branches are never deleted; origin branch deletions are optional and each requires its own approval gate. Release tagging, version bumping, and publishing are out of scope and belong to the separate aiwfx-release skill.