dot-ai-changelog-fragment

You can automate changelog fragment creation by reading PRDs to extract problem statements, solutions, and technical details, then generating formatted `.md` files in the `changelog.d/` directory with appropriate documentation links.

Changelog fragment types like feature or bugfix are determined automatically by reading the configuration defined in your project's `pyproject.toml` file, ensuring the generated release notes match your project's specified conventions.

You need to create a changelog fragment when a PR is ready for review, allowing you to generate the changelog entry alongside the code to ensure release notes are accurate and up-to-date before the release is finalized.

Yes, the workflow integrates with towncrier conventions by writing `.md` files to the `changelog.d/` directory using a specified naming convention, allowing you to compile formal release notes from PRD-driven entries.

Automating release notes generation is best handled by extracting technical details and user impact directly from PRDs during the `/prd-done` workflow, creating standardized changelog fragments to maintain consistency across releases.