Closing an epic

An epic is done when its feature works, not when its issues are closed. rafa epic close <n> is one command that runs a small workflow to check the difference: it refuses while any member is open, then turns each acceptance criterion into a check and runs the checks against the default branch.

What rafa epic close runs, in its default order.−100%+FitClose

The steps

1. Members. While any member of the epic is open, the close is refused with exit code 2, naming them. Nothing has been spent yet.
2. A verification plan. One Claude Code session plans a check for each acceptance criterion in the epic's body, or names the criterion uncheckable with a reason.
3. Uncheckable criteria. Any criterion that could not become a check refuses the close before a check runs, unless you pass --accept-unchecked, which closes over it and names it in the comment.
4. Checks. Each check runs as its own session in a detached worktree of origin/main, so your checkout is not touched.
5. Failures. Each failed check is filed as a bug, or, when its criterion names only documentation, added as a line to the release's stale-docs issue. Any failure refuses the close.
6. The close. The epic is closed as completed, with a comment naming each criterion. What its members cost, summed from the effort store, is printed beside the epic's estimate.

What it spends

One verification planning session and one session per check, and nothing while a member is still open. It needs gh and Claude Code (Prerequisites).

rafa epic close 40
rafa epic close 40 --accept-unchecked

The full reference, with the other epic actions, is on rafa epic.