• Take a look at the description of the work done here for the project:
  https://issues.redhat.com/browse/CCSAI-5
• ACM release note process for GA is simple: The writer summarizes the topic after writing about the feature as part of the release. This is a more efficient process than some other teams, so we are good on that part.
• What this tool can potentially help with is the z-stream process. Currently that process is in the playbook: https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit?tab=t.0#heading=h.ou8wsqlk362z
• To summarize:
  Release manager opens an issue for z-stream (Errata) focal (Jake).
  Release manager adds what should be released to the customer and lists the issues for Jake in the advisory.
  Jake uses those issues to seek a quick summary that is added by the engineers as they close and summarize the bug.
• The problem is that often the summary requires some chasing down. I have even gone in to pull requests in the past to get that info.

Use this issue to take some time and see how the tool works with one of those issues for a z-stream–I recommend using a release that has already gone out. 

Use a engineering bug to see if we can get a summary without having to ask for one. If it works well, see how we can change the process and take out the need for a manual summary in the issue.