What problem does it solve? Cutting a GAIA release involves many error-prone manual steps β drafting release notes, opening a release PR, verifying the merged commit, pushing a tag, monitoring the publish pipeline, and writing the Discord announcement β where a single mistake (like a reverted version bump or an unescaped MDX character) can break the release. ## Core Features & Use Cases - Phased release checklist with hard gates: Six phases (notes, PR, pre-tag verification, tag, publish monitoring, announcement) each pause for explicit user approval before any irreversible action like pushing a tag. - Resume detection: Re-invocation safe β inspects git tags, PRs, and GitHub releases to detect where a multi-day release flow left off and resumes at the correct phase. - House-style release notes: Enforces a strict bulleted, plain-language notes format with word budgets, MDX escaping for the changelog, and validation via validate_release_notes.py plus mintlify validate. - Use Case: A maintainer says "release v0.17.5" and the skill drafts the notes, opens the release PR, verifies the merged commit builds green, pushes the annotated tag, watches the publish workflow, and drafts the Discord announcement β stopping at every gate for approval. ## Quick Start Ask the assistant to cut a GAIA release for a specific version, for example: "Release v0.17.5 using the gaia-release skill."