release-plan

Automate release ledger creation by interviewing operators and cross-referencing changelog history.

2|Updated Jun 24, 2026

Search Tags:#changelog #versioning #documentation #release #ledger #pdda

Ready to run

npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill release-plan-hypercart-dev-tools

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-plan
Source: https://github.com/Hypercart-Dev-Tools/pdda/tree/main/SKILLS/RELEASE-PLAN
Command: npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill release-plan-hypercart-dev-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of maintaining a release ledger by automating the versioning, cross-referencing, and documentation required to keep RELEASES.md accurate and up-to-date.

Core Features & Use Cases

Automated Ledger Management: Interviews the operator to generate standardized release blocks, ensuring consistency across the project.
Intelligent Backfilling: Scans existing CHANGELOG.md entries to synthesize descriptions for past releases that were never formally recorded.
Version Logic: Proposes canonical version numbers based on existing project history, preventing manual calculation errors.

Quick Start

Ask the release-plan skill to backfill missing release entries from the changelog.

Frequently Asked Questions about release-plan

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

FAQPage Schema

How do I automate a release ledger from existing changelog history?▼

Automate a release ledger by scanning existing CHANGELOG.md entries to synthesize descriptions for past releases. The Skill interviews operators to generate standardized release blocks and cross-references changelog history to keep RELEASES.md accurate.

How do I backfill missing release entries in my project documentation?▼

Backfill missing release entries by scanning your existing CHANGELOG.md entries to intelligently synthesize descriptions for past releases that were never formally recorded, ensuring your project documentation remains complete and consistent.

How does automated versioning determine the next canonical version number?▼

Automated versioning proposes canonical version numbers based on existing project history, preventing manual calculation errors. It cross-references your changelog history and release ledger to calculate the correct semantic version increment.

Do I need a specific repository structure to maintain a release ledger?▼

Yes, maintaining a release ledger requires a PDDA-compliant repository structure and access to project-level markdown files for deterministic data synthesis. This ensures consistent version tracking and accurate release documentation.

What is the best way to standardize release blocks across a software project?▼

Standardize release blocks by interviewing operators to generate consistent entries across the project. This eliminates the friction of manual versioning and cross-referencing, keeping your release documentation uniform and accurate.

What are the limitations of automating release documentation from a changelog?▼

Automating release documentation requires a PDDA-compliant repository structure and access to project-level markdown files. Without these prerequisites, the Skill cannot deterministically synthesize data or backfill missing release entries accurately.