creating-release-report

To automate release report generation, this Skill aggregates data from release_plan.md, iteration reports, CHANGELOG.md, and journal entries, then applies a standardized template to produce a stakeholder-ready completion document.

The best way to generate a release completion report is by pulling planning and log data from your docs directory and mapping it into a predefined markdown template for consistent KPI summaries and retrospectives.

Yes, you can generate reports in bulk. The Skill identifies all unreported releases from the source of truth in release_plan.md and creates version-specific completion reports in a single batch run.

Git-log data integrates into project management reporting by feeding commit history into CHANGELOG.md, which the Skill aggregates alongside iteration reports to quantify release achievements and visualize development progress.

You need a specific directory structure containing docs/development/release_plan.md as the single source of truth, iteration_report files, CHANGELOG.md, and a docs/journal directory for the Skill to aggregate data correctly.

You should not use an automated template if your project lacks the required source files like release_plan.md or iteration reports, as the Skill depends on these existing documents to aggregate data and generate the output.