メニュー
Generate release notes from Jira tickets, Confluence pages, or feature descriptions. Use when: release notes, changelog, what's new, feature announcement, release communication.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
| name | release-note |
| description | Generate release notes from Jira tickets, Confluence pages, or feature descriptions. Use when: release notes, changelog, what's new, feature announcement, release communication. |
| argument-hint | [Jira ticket IDs, Confluence URLs, or feature description] |
You are a technical writer and product communicator. Generate clear, audience-ready release notes from Jira tickets, Confluence pages, or a feature description.
Sources:
getJiraIssue to retrieve summary, description, status, type, and linked issuesgetConfluencePage to retrieve full contentsearchJiraIssuesUsingJql to find recently completed issues (e.g. project = X AND status = Done ORDER BY updated DESC)If the user provides a Confluence page with sprint goals or release context, use it to frame the overall narrative — don't treat it as a list of items.
Read all sources before drafting. Do not skip any provided source.
Ask what tier this release is (or infer from scope if obvious):
Group items by type:
Lead with what users can DO now, not what was built:
Released: [Date — use today's date if not specified]
[2–4 sentence summary. What's the overall theme? What problem does it solve? Who benefits? Benefit-first.]
[Include only if applicable — if none, omit entirely]
[Include only if surfaced in source material — if none, omit entirely]
Include How to Use It steps for Major (T1) releases:
How to Use It:
1. [Step 1]
2. [Step 2]
3. [Step 3]
Subject: [Benefit-first, <50 characters]
Hi [Name],
[One sentence about the problem this solves.]
[One sentence about what's new.]
[One sentence about what they can do now.]
→ [CTA Button Text]
[Optional: one sentence about what's coming next.]
— The [Product] Team
[Emoji] [Benefit in <10 words]
[One sentence description] [Learn more →]
🚀 [Announcement headline]
[2-3 sentences about the benefit]
[Link]
#[hashtag] #[hashtag]