Skip to content
Back to skills

Release Notes

ASecurity

Generate audience-targeted release announcements. Specify the audience (customers, internal team, investors, social media) and optionally a version or scope. Use after shipping to announce what was built.

  • 14 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
content-marketinggogitapi

Works with

  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add pcatattacks/solopreneur-plugin --skill release-notes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Release Notes?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Release Notes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pcatattacks-release-notes/badge)](https://www.skillsdirectory.com/skills/pcatattacks-release-notes)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: release-notes
description: Generate audience-targeted release announcements. Specify the audience (customers, internal team, investors, social media) and optionally a version or scope. Use after shipping to announce what was built.
argument-hint: audience (customers, engineers, etc.)
---

# Release Notes: $ARGUMENTS

You are generating release announcements. Parse `$ARGUMENTS` for:
- **Audience**: customers, internal team, engineers, investors, social media (default: customers)
- **Version/Scope**: Optional version number or feature scope

## Process

1. Gather context:
   - Read recent git log for commits and changes
   - Read any specs in `.solopreneur/specs/` relevant to recent work
   - Read any plans in `.solopreneur/plans/`
   - Check for existing release notes in `.solopreneur/releases/`

2. Delegate to the `@content-strategist` subagent to generate audience-appropriate content:

   **For customers**:
   - Tone: Exciting, benefit-focused, clear
   - Format: What's New → Why It Matters → How to Use It
   - Focus on user impact, not technical details

   **For internal team / engineers**:
   - Tone: Technical, specific, actionable
   - Format: Changelog with categories (Added, Changed, Fixed, Removed)
   - Include file paths, API changes, migration notes

   **For investors**:
   - Tone: Business impact, growth-oriented
   - Format: Key Metrics Impact → Strategic Significance → What's Next
   - Connect features to revenue, retention, or market positioning

   **For social media**:
   - Tone: Punchy, shareable, hook-driven
   - Format: 3 tweet-length announcements + 1 longer LinkedIn/blog post
   - Include suggested hashtags and CTAs

3. Save to `.solopreneur/releases/{date}-{audience}-{slug}.md` (create the directory if needed).

4. Present the release notes to the CEO for review before publishing.

5. End with the next step prompt:
   ```
   -> Release notes ready. What's next?
      Start your next feature:
      /solopreneur:discover [next idea]

      Or tell the story of what you just built:
      /solopreneur:story
   ```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.