How does the skill identify which changes to include?

It uses git tags to determine a starting point and analyzes all commits between that tag and the current state, mapping them to relevant project documents.

What information is included in the generated release plan?

The plan includes a summary of changes since the last tag, affected modules, new features, improvements, architectural decisions (ADRs), and a list of outstanding items that need resolution.

Where is the generated release plan saved?

The skill saves the plan as a Markdown file within a local .release/ directory in your repository, making it easy to commit and review.

Do I need the GitHub CLI to use this skill?

While not strictly required, the GitHub CLI (gh) is highly recommended as it allows the skill to pull enriched context from Pull Requests for more detailed summaries.

Release Plan Drafter

Name: Release Plan Drafter
Author: alexnodeland

byalexnodeland

•

Deployment & DevOps

Drafts comprehensive, human-reviewable release plans by summarizing changes and identifying outstanding tasks since the last git tag.

The Release Plan Drafter automates the creation of structured release documentation by analyzing git history, mapping commits to project documents, and identifying affected modules. It provides teams with a clear overview of new features, improvements, and architectural decisions while highlighting outstanding items that require attention before a release is finalized. By integrating with tools like GitHub CLI and local version-bump scripts, it ensures that your release process is specification-driven and your documentation remains consistent with actual codebase changes.

Key Features

01Module-specific change grouping and version detection

02Automated change summarization based on git tags and commit history

03GitHub CLI integration for enriched pull request context

04Readiness checking for non-terminal documents and outstanding tasks

05Template-based markdown generation for team review

063 GitHub stars

Use Cases

01Generating a structured summary of changes for team review before a production release

02Identifying unmerged features or blocking tasks that prevent a release

03Maintaining a consistent release history across complex, multi-module repositories

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add alexnodeland/principled release-plan

For use in Claude.ai and ChatGPT

Download Skill