# How to Generate Release Notes from Tickets Using the pm-execution Plugin > Learn how to generate release notes from tickets using the pm-execution plugin. Convert raw ticket exports into categorized markdown release notes effortlessly with this powerful tool. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: how-to-guide - Published: 2026-06-21 --- **The pm-execution plugin converts raw ticket exports into categorized markdown release notes by processing input through the `/sprint release-notes` command and the declarative skill definition in [`pm-execution/skills/release-notes/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/release-notes/SKILL.md).** The **pm-execution** plugin in the **phuryn/pm-skills** repository provides a streamlined workflow to generate release notes from tickets using the Claude-plugin architecture. This system transforms unstructured ticket data from Jira, Linear, or CSV exports into polished, user-facing documentation without requiring any code modifications. ## Understanding the pm-execution Plugin Architecture The pm-execution plugin follows the standard **Claude-plugin** architecture used throughout the pm-skills repository. Each capability is defined declaratively in markdown files that the runtime reads at load time, enabling data-driven behavior changes without redeployment. ### Skill Definition in SKILL.md The release-notes capability is declared in [`pm-execution/skills/release-notes/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/release-notes/SKILL.md). This file defines the skill name, description, and step-by-step instruction set that guides the transformation process. According to the source code, the skill instructions direct the system to gather material, categorize changes, write user-focused entries, and format the final markdown output. ### Command Entry Point in sprint.md The public interface for this functionality resides in [`pm-execution/commands/sprint.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/sprint.md). The `/sprint` command supports three modes: plan, retro, and release-notes. When you invoke `/sprint release-notes`, the command forwards your ticket data to the release-notes skill defined in the corresponding SKILL.md file. ## How to Generate Release Notes from Tickets The workflow follows a strict three-phase pipeline: input collection, intelligent transformation, and formatted output generation. ### Step 1: Invoke the Release Notes Command Initiate the process by typing the command in your Claude interface: ```text /sprint release-notes ``` The command definition in [`pm-execution/commands/sprint.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/sprint.md) (lines 48-55) specifies that the system will prompt you to paste your ticket data. This Step 1 collects the raw material required for processing. ### Step 2: Provide Ticket Data Input Paste your ticket data directly after the command. The plugin accepts multiple formats including Jira exports, Linear issue lists, or CSV data. For example: ```text - KEY-101: Add export-to-CSV button on the dashboard (Feature) - KEY-102: Reduce load time of the reports page from 8s to 2s (Improvement) - KEY-103: Fix crash when uploading large files (Bug) ``` The skill processes this raw text to extract three core fields from each ticket: *what changed*, *who it affects*, and *why it matters* (lines 18-22 of [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md)). ### Step 3: Automated Categorization and Formatting The plugin automatically classifies each change into standardized categories defined in lines 23-28 of the skill definition: - **New Features** - **Improvements** - **Bug Fixes** - **Breaking Changes** - **Deprecations** Using the markdown template defined in lines 45-59 of [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) (also reproduced in lines 66-84 of [`sprint.md`](https://github.com/phuryn/pm-skills/blob/main/sprint.md) for reference), the system assembles the final document. The output includes a "What's New" header, highlights section, and categorized bullet points with user-focused descriptions. ## Customizing the Release Notes Output Because the pm-execution plugin uses a **data-driven architecture**, you can modify output categories or adjust the tone by editing the [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) template. No code compilation or deployment is required; the plugin loads the updated skill definition automatically on the next runtime initialization. This extensibility allows teams to add custom categories like "Security Updates" or "Performance Optimizations" by updating the categorization logic in lines 23-28. ## Complete Workflow Example Below is a complete example showing input transformation through the pm-execution plugin: **Command invocation:** ```text /sprint release-notes ``` **Sample input (Linear export):** ```text - KEY-101: Add export-to-CSV button on the dashboard (Feature) - KEY-102: Reduce load time of the reports page from 8s to 2s (Improvement) - KEY-103: Fix crash when uploading large files (Bug) ``` **Generated markdown output:** ```markdown ## What's New — v1.4.0 (2024-06-21) ### Highlights Dashboards now let you export data directly to CSV, and the reports page loads three times faster. ### New Features - **Export to CSV** — Users can now download dashboard data as a CSV file, making it easier to share insights with teammates. ### Improvements - **Reports page performance** — Page load time dropped from 8 seconds to 2 seconds, reducing waiting time for analysts. ### Bug Fixes - Fixed a crash that occurred when uploading large files, improving reliability for power users. ``` The same workflow applies to JIRA XML or CSV exports; the skill requires only the raw text to extract core fields and generate the structured document. ## Summary - **The pm-execution plugin** uses declarative [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files to define transformation logic without code changes. - **Invoke the command** using `/sprint release-notes` and paste ticket data from Jira, Linear, or CSV sources. - **Automatic categorization** sorts changes into New Features, Improvements, Bug Fixes, Breaking Changes, or Deprecations based on lines 23-28 of the skill definition. - **Template-driven output** generates markdown using the structure defined in lines 45-59 of [`pm-execution/skills/release-notes/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/release-notes/SKILL.md). - **Zero-code customization** allows modification of categories and tone by editing the markdown skill file. ## Frequently Asked Questions ### What ticket formats does the pm-execution plugin support? The plugin accepts raw text from Jira exports, Linear issue lists, CSV files, or any plaintext ticket dump. According to the implementation in [`pm-execution/commands/sprint.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/sprint.md), the system collects the pasted material in Step 1 (lines 48-55) and processes it regardless of the original source format, extracting relevant fields through pattern matching defined in the skill logic. ### How do I modify the release notes categories? Edit the [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) file located at [`pm-execution/skills/release-notes/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/release-notes/SKILL.md). Lines 23-28 define the available categories (New Features, Improvements, Bug Fixes, Breaking Changes, Deprecations). You can add, remove, or rename categories in this file, and the plugin will apply the new classification scheme on the next load without requiring code deployment. ### Can I use the pm-execution plugin outside of Claude? The pm-execution plugin is built specifically for the Claude-plugin architecture used in the phuryn/pm-skills repository. While the skill definitions are written in markdown, the runtime environment requires the Claude execution context to process the [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) instructions and generate the release notes output. ### Where is the release notes template defined? The primary template definition resides in lines 45-59 of [`pm-execution/skills/release-notes/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/release-notes/SKILL.md). Additionally, a reference copy appears in lines 66-84 of [`pm-execution/commands/sprint.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/sprint.md) for quick consultation. Both locations define the markdown structure used for the final output, including headers, highlight sections, and categorized bullet points.