paperclip-close-epic

paperclip-close-epic

Verifies that every child issue of an epic is in done status, composes a structured closing summary, and transitions the epic to done. Produces a document artifact summarizing shipped work before closing.

When to use

Run this skill when:

• The Scrum Master heartbeat detects that all tracked children of an epic are done.
• A human operator or coordinator agent wants to formally close an epic and archive its outcomes.
• You are the Scrum Master and the heartbeat identified a candidate epic for closure.

Do not run this skill on an epic that has any child in todo, in_progress, in_review, or blocked. The skill will abort if that check fails.

Step 1 — Fetch the epic

paperclip_get_issue  { issueId: "<epic-id>" }

Confirm the issue type is epic (or the equivalent parent-type in your Paperclip configuration). Record title, projectId, goalId, and status. If the epic is already done or cancelled, exit — nothing to do.

Step 2 — List all children

paperclip_list_issues does not accept a parentId filter. Use one of these strategies to find child issues:

Strategy A — filter by project, then check parentId in results (fastest for small projects):

paperclip_list_issues  { projectId: "<epic-project-id>", limit: 100, offset: 0 }

Filter the returned issues client-side: issues.filter(i => i.parentId === epicId).

Strategy B — full-text search for the epic identifier:

paperclip_list_issues  { q: "<PAP-N>", limit: 100, offset: 0 }

Strategy C — filter by goalId if the epic and all children share a goal:

paperclip_list_issues  { goalId: "<epic-goal-id>", limit: 100, offset: 0 }

Then filter client-side by parentId. Use Strategy A unless the epic spans multiple projects.

If no children are found, log a warning and ask the operator before closing — an epic with no children may indicate a data problem.

Step 3 — Verify all children are done

For each child, check status === "done". If any child is not done: