What problem does it solve? MariaDB DOCS release epics accumulate auto-created child tickets parked in On Hold long after the upstream MDEV development work has shipped, and nothing moves them back automatically. This Skill sweeps those tickets, determines per ticket whether the upstream work is actually done, and releases the ready ones for writing. ## Core Features & Use Cases - Evidence-backed tiering: Resolves each ticket's primary MDEV, checks the public jira.mariadb.org status, resolution, and fix version, and inspects a local MariaDB source clone for merged or reverted commits, classifying tickets as READY, CANDIDATE, NOT READY, or AMBIGUOUS. - Dry-run by default: Prints a triage table and proposed comment briefs, then waits for explicit approval before posting a Jira comment and transitioning tickets from On Hold to TODO. - Revert and conflict detection: Flags reverted work, series mismatches, and negative human signals in MDEV comments so writers are never sent to document pulled features. - Use Case: Before planning a documentation sprint, ask which doc tickets in the 13.1 release epic are ready to write; the Skill reports which On Hold children have shipped upstream work and, with approval, promotes them to TODO. ## Quick Start Ask the assistant to triage DOCS-6084 and report which On Hold doc tickets are ready to write.
