paperclip-release-flow

paperclip-release-flow

Produces a structured CHANGELOG document from all issues closed under a goal, updates the goal status to reflect the release, and posts stakeholder notifications. This is a Paperclip-level release tracking workflow — it does not interact with git tags or npm. For the git/npm release, see the repo's CI release pipeline.

When to use

Run this skill when:

• A sprint or milestone is complete and you need a structured record of what shipped.
• You are preparing to cut a version and need a CHANGELOG document before notifying stakeholders.
• The Scrum Master or PM asks for a release summary after all epics under a goal are done.

Do not run this skill on a goal that still has open issues. Confirm all epics and their children are done first (use paperclip-close-epic for any unclosed epics).

Step 1 — Fetch the goal

paperclip_get_goal  { goalId: "<goal-id>" }

Record title, description, status, and projectId. If status is already done, this skill may be running redundantly — verify with the operator before proceeding.

Step 2 — List all issues under the goal

paperclip_list_issues  { goalId: "<goal-id>" }

Collect all issues. Group them by type: feature, bug, chore, docs. Filter to status: "done" only — open issues should have blocked the release; log any found and flag them to the operator.

Step 3 — Compose the CHANGELOG

Build the CHANGELOG body using this structure:

# CHANGELOG — <goal title>

**Released:** <ISO date>
**Goal:** <goal description, 1–2 sentences>

## Features

- PAP-XX — <title>
- PAP-YY — <title>

## Bug Fixes

- PAP-ZZ — <title>

## Chores & Maintenance

- PAP-AA — <title>

## Documentation

- PAP-BB — <title>

## Known Limitations

<If any issues were explicitly deferred or descoped, list them here with a note. Otherwise omit this section.>

Omit any section that has no items. Do not fabricate entries.

Step 4 — Create the CHANGELOG document

paperclip_upsert_document  {
  title: "CHANGELOG: <goal title>",
  content: "<CHANGELOG markdown>",
  goalId: "<goal-id>"
}