scrips-stack-release

Automating release management for team-kit updates requires a skill that generates release notes, posts education material, and tracks acknowledgments. This skill triggers on repository changes, appending notes to RELEASES.md and mirroring them to Confluence.

Tracking team acknowledgments for a change log is handled by maintaining an open-loops ledger. The skill posts acknowledgment requests to a team channel and keeps the ledger open until every member explicitly acknowledges the update.

To automatically generate education material from repository changes, you need a workflow that detects new, changed, or removed skills. This skill crafts friendly education content describing what changed and why it matters for engineers.

Mirroring release notes to Confluence and onboarding docs is supported through cross-channel mirroring. The workflow appends updates to RELEASES.md and mirrors the release log to your designated documentation platforms.

The release workflow does not require manual triggers to post to the team channel. It is triggered automatically by changes to the team kit repository, specifically when new, changed, or removed skills are detected.