CLUE-599 Expand Release Instructions

[tealefristoe]

No description provided.

[scytacki]

Looks good.

Next time we do a release that isn't rushed. We should follow an approach that Doug has done. He has had Claude do the release by telling it to do each step. In our case we could point Claude at this file and tell it to do the steps with confirmation from us as it goes. For CLUE in addition, we can instruct Claude to:

• run the script to check the release, and iterate over the PRs and Stories that need changes. It should ask how to handle each issue, and we should instruct it how to update the Jira story or PR.
• after completing this it can find if there are any rule, function, or index changes. And then to also verify if those changes are safe to deploy to Firebase before the version is released.
• create the release notes in GitHub, and post them to Slack
  There are probably additional checks on top of these.

After Doug did this with Claude "manually", then he's asked Claude to make a skill for the release. I've reviewed a couple of these skills and they've looked really good. A key part is the "manual" process so Claude has in its context a worked example of doing a release. This skill should help us to not forget steps of the release. And we can expand the skill as we identify new things that we should be doing as part of the release.

We could even take it further and have Claude post to Slack when we need input from product owners or developers. If that works well, we could eventually turn this into an agent that can wait for responses to these slack messages and then move the process along. So then it could then manage all of this for us, and we just review summaries and approve the next step.