skills.rest
petekp
petekpCOMMUNITY
Explore all skills by this author →
Website𝕏@petekpGitHub

release-note-flow

Draft release notes from a change summary using a structured workflow.

Updated Apr 18, 2026
Search Tags:#verification#release notes#review#software delivery#drafting#change summaries
One-click install
npx skills add https://github.com/petekp/circuit-next --skill release-note-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-note-flow
Source: https://github.com/petekp/circuit-next/tree/main/docs/release/proofs/runs/customization/custom-home/drafts/release-note-flow
Command: npx skills add https://github.com/petekp/circuit-next --skill release-note-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a raw change summary into clear, publishable draft release notes so you do not have to manually structure and rewrite updates for stakeholders.

Core Features & Use Cases

  • Change-to-notes drafting: Produces a release-notes draft from an input change summary/task.
  • Structured multi-stage workflow: Frames the brief, plans the notes, relays drafting/implementation work, verifies output, and reviews before closing.
  • Mode-driven thoroughness: Runs with controllable rigor (lite/standard/deep) to match speed vs. quality needs.

Use case example: After merging a batch of changes, provide the summary and get a draft release-note document ready for further editing or approval.

Quick Start

Run the release-note-flow with your change summary as the goal.

Frequently Asked Questions about release-note-flow

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

FAQPage Schema
How do I generate release notes from a change summary?▼

To generate release notes, provide your change summary as input and the Skill drafts a structured, stakeholder-friendly document by running a frame-plan-act-verify-review-close workflow.

What is the best way to draft release notes for software delivery batches?▼

Drafting release notes through a structured multi-stage workflow converts raw feature, fix, and refactor batches into clear, publishable communication ready for stakeholder review and approval.

Do I need to manually verify the generated release notes draft?▼

Manual verification is minimized because the workflow automatically applies verification and review passes to the draft release notes output before closing, ensuring the change summary is accurately reflected.

Can I control the thoroughness of the release notes drafting process?▼

You can control drafting thoroughness using mode-driven rigor settings, selecting lite, standard, or deep modes to match your required balance between generation speed and output quality.

Does this approach work for compiling both feature updates and refactoring changes?▼

Yes, the drafting process applies to software delivery workflows compiling mixed batches, translating feature updates, bug fixes, and refactoring changes into a consistent release-notes format.

Related Skills

Explore More Content & Communication Skills→
nuoyanruoshuinuoyanruoshui
47

changelog

Generate structured internal and player-facing changelogs from git commits and project documentation.

Community
Advanced
typemdtypemd
9

create-release

Gather closed issues and commits to draft release notes and create a GitHub draft release.

Official
Advanced
monaccodemonaccode
30

changelog-automation

Generate change logs from Git commit messages in Keep a Changelog format.

Official
Intermediate
zhuangfanupupzhuangfanupup

project-summary-writer

Summarize repository changes into structured delivery notes and release guidance.

Community
Intermediate