wrap-up

You can generate a changelog automatically by correlating your PRD success criteria, closed issues, and git commit history. The Skill reads these inputs to weave a narrative changelog file that highlights how implemented work maps to product requirements.

Mapping git log history to PRD success criteria involves reading your product requirements document and closed issues alongside your repository commits. The Skill correlates these elements to align evidence with each criterion and highlights matching entries in the final changelog.

Yes, you need specific input files to create a feature changelog: a PRD file at features/<slug>/prd.md, completed issue files in features/<slug>/issues/done, and an accessible repository git log. These three inputs are required to synthesize the narrative.

To compile completed issues and git history into a review-ready changelog, the Skill reads your done issues and commit history, weaves them into narrative sections, and generates a structured markdown file at features/<slug>/changelog.md ready for immediate review.

Use an automated changelog generator when your feature lifecycle reaches a state where a PRD exists and there are closed issues and git commits to map to each criterion. It is designed for post-AFK loop compilation to synthesize development evidence into a narrative.