Phase 0 for GenStudio monthly release notes: resolve the Jira work ticket, fetch the release ceremony wiki, parse GA and Beta feature group tables, pull linked KT pages via Confluence MCP, and hand structured inputs to generate-release-notes. Use when Jira and Confluence MCP are available and the user is adding or rotating release notes.
Installation
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Phase 0 for GenStudio monthly release notes: resolve the Jira work ticket, fetch the release ceremony wiki, parse GA and Beta feature group tables, pull linked KT pages via Confluence MCP, and hand structured inputs to generate-release-notes. Use when Jira and Confluence MCP are available and the user is adding or rotating release notes.
Jira ticket key from branch name (GS-#####), user input, or ticket description
Workflow checklist
Resolve Jira ticket — jira_getIssue with issueKey. Read description for the ceremony wiki link and release month.
Locate ceremony page — use wiki URL from ticket; fallback CQL: title ~ "YYYY/MM Release Ceremony" AND space = GenStudio.
Fetch ceremony body — confluence_getContent with bodyMode: storage (required; text loses KT links and table structure).
Parse feature groups — extract rows from GA Release Features and Beta Release Features (see reference.md).
Apply inclusion filter — per user scope (see reference.md); confirm Beta row count (may be zero).
Resolve KT pages — confluence_searchContent per KT title; confluence_getContent with bodyMode: text.
Extract KT fields — Description, Elevator pitch, Feature(s) delivered, Problem statement, Release Type & Date.
Set Beta flags — requiresBetaBadge: true for Beta section rows or GA-table rows with Type Beta.
Hand off to generate-release-notes with structured row list (no wiki/Jira refs in shipped copy).
Beta labeling (handoff to generate skill)
When requiresBetaBadge: true, the downstream ### section must include immediately under the heading:
[!BADGE Beta]{type=Informative tooltip="This feature is currently in Beta, so some functionality may be limited or subject to change."}
Do not add italic scheduling disclaimers for Beta; the badge is the supported pattern.
Prohibited in shipped release notes
Internal IDs, wiki URLs, KT citations, and Jira keys stay in this ingest phase only. Summarize user-facing outcomes in the public page per generate-release-notes prohibited content.
Fallback
If MCP calls fail, ask the user to paste ceremony and KT content, then continue with generate-release-notes using reference.md KT field mapping.
