plot-release

Name: plot-release
Availability: InStock
Author: plot

Verify release readiness and collect changelog entries from delivered plans.

2|3|Updated Mar 13, 2026

Search Tags:#git #changelog #release management #version control #release process

Ready to run

npx skills add https://github.com/plot-pm/plot --skill plot-release-plot-pm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plot-release
Source: https://github.com/plot-pm/plot/tree/main/skills/plot-release
Command: npx skills add https://github.com/plot-pm/plot --skill plot-release-plot-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the release process by verifying release readiness and guiding the release steps without executing them automatically, ensuring accurate release notes and proper hand-off to the project's release process.

Core Features & Use Cases

Release Readiness Verification: Ensures that all delivered plans are ready for release.
Changelog Collection: Collects changelog entries from delivered plans.
Cross-Check and Recommendations: Provides a summary of the release process and suggests the next steps.
Versioning and Tagging Guidance: Guides the user through version bumping and tagging without automating these steps.
Use Case: Imagine you have a series of feature and bug fixes ready for release. Use this Skill to verify that everything is in place, collect the necessary information, and get recommendations for the release process.

Quick Start

Run the plot-release skill to start the release process.

Frequently Asked Questions about plot-release

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

FAQPage Schema

How do I verify release readiness and collect changelog entries before tagging a version?▼

Release readiness verification ensures delivered plans are complete by cross-checking actual work and collecting changelog entries before proceeding to version bumping and tagging.

Can I automate git version bumping and tagging directly from my changelog collection?▼

No, this release process guides users through version bumping and tagging without executing the steps automatically, ensuring proper hand-off to your project's specific release process.

Do I need the gh CLI to manage my version control and release process?▼

Yes, you need both git and the gh CLI installed to handle forge operations, version detection, and cross-checking delivered plans against actual repository work.

Does this release management workflow support pre-release versions?▼

No, this release management workflow does not support pre-release versions, focusing solely on standard version detection and release readiness verification for delivered plans.

What is the best way to streamline release processes from delivered plans in Claude Code?▼

Streamlining release processes from delivered plans involves verifying readiness, collecting changelog entries, and guiding version bumping steps designed specifically for Claude Code and Cursor environments.

Why does my release process require cross-checking delivered plans against actual work?▼

Cross-checking delivered plans against actual work validates release readiness, ensuring that collected changelog entries accurately reflect the repository state before version tagging.