generate-changelog

To generate a changelog from project specs, run a command targeting your planning directory to extract meaningful changes from documentation and append them to your CHANGELOG.md file. This automates release notes creation by reading your project records directly.

Automated changelog generation uses a prepend-only update model, meaning it preserves existing CHANGELOG.md content while adding new entries at the top. This ensures your historical version control records remain intact without manual editing.

Generating release notes from planning docs requires a Git repository containing spec-based project records like milestones and planning documents. You must point the generation script to your planning root directory to extract the relevant changes.

Use automated documentation for version control milestones when your project reaches a new phase and you need to update release notes. It extracts changes from your specs and planning docs to keep records current without manual editing.

Yes, you can generate a changelog from markdown planning files without manual editing by running a script that parses your project specifications. It automatically extracts meaningful changes and appends them to your documentation.