issue-draft-release-noteslisted

# Issue — Draft Release Notes Read-only drafting of a customer-facing release note for a Jira ticket. Gathers ticket context and related MR code changes, synthesizes a release note matched to the audience, runs a quality pass, and (only on opt-in) posts it back to the ticket. **Read-only by default.** The skill never modifies code, MRs, Confluence, or Jira fields. The single permitted write is in Phase 6 — and only after explicit user opt-in: posting the note as a Jira comment, or setting a Release Notes field. ## Input A Jira ticket key — pattern `[A-Z][A-Z0-9]+-\d+` (e.g. `PRJ-1234`). Extract from the user's message. If no key is present, ask for one. Default project key (if the user gives only a number) is read from memory (`reference_jira_default_project.md`). ## Workflow ```text Release-Notes Progress: - [ ] Phase 1: Gather ticket context - [ ] Phase 2: Find & analyze related MRs / code changes - [ ] Phase 3: Determine audience & note type - [ ] Phase 4: Draft the release note - [ ] Phase 5: Quality pass (clarity-council + writing-humanize) - [ ] Phase 6: Optionally publish back to the ticket (user opt-in) ``` ### Phase 1 — Gather ticket context - `jira_get_issue` — summary, description, issue type, status, priority, components, labels, **fix version(s)**, affected version, resolution. - `jira_get_comments` — capture what was actually implemented vs. originally scoped; watch for "done / shipped in" notes. - `jira_get_remote_links` — capture linked GitLab MR URLs