菜单
Generate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate A/B copy variants for any piece of marketing copy with a hypothesis per variant. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", or wants to test copy before publishing. Produces 3-5 variants per copy element with angle, hypothesis, and expected audience response. Reads brand voice and ICP from knowledge/.
Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/.
Plan a marketing campaign end-to-end using Allan Dib's Before/During/After framework (The 1-Page Marketing Plan). Produces a phase-specific campaign brief with goal, audience, message, channels, assets, timeline, budget, and success metrics. Use when the user asks to plan a campaign, brief a campaign, "we need a campaign for X", launch plan, GTM plan, marketing plan for <product>, demand gen plan, or any multi-channel marketing initiative. Reads ICP, services, and KPIs from knowledge/.
Write customer case studies and success stories using the Situation-Complication-Resolution (SCR) narrative framework and Barbara Minto's Pyramid Principle (conclusion first). Produces case studies where the headline states the result, the complication makes readers recognize their own situation, and every paragraph advances the story. Use when the user asks for a case study, customer story, customer success story, win story, reference write-up, or "turn this customer into a case study". Reads brand voice and service catalog from knowledge/.
Analyze competitors using Blue Ocean Strategy's ERRC Grid and Strategy Canvas (W. Chan Kim and Renee Mauborgne) to identify uncontested market space, not just who is better on the same axes. Produces an ERRC Grid, Strategy Canvas, positioning matrix, messaging comparison, and differentiation map. Use when the user asks for competitive analysis, competitor research, "how do we compare to X", positioning vs competitors, market landscape, "analyze our competition", "where is the blue ocean", or wants to update competitor docs. Writes to knowledge/markets/competitors.md.
Take one piece of long-form content (blog post, podcast, talk, article, newsletter) and turn it into a multi-channel asset pack using the STEPPS framework (Jonah Berger, Contagious) to make each derivative asset more shareable. Use when the user says "repurpose this", "turn this into LinkedIn/Twitter/etc", "atomize this", "break this down for social", "create derivative content from X", "make a content pack from this", or wants to maximize output from one input. Each channel is mapped to its strongest STEPPS element. Orchestrates linkedin-post, content-writer, and other skills.
| name | release-notes-writer |
| description | Generate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets |
Generate structured release notes for each release cycle. Produces both user-facing (what changed and why it matters) and internal (technical changes, migration steps) release notes.
# [Product Name] — Release Notes {version}
**Release Date:** {DD-MM-YYYY}
**Environment:** {Production / Staging / UAT}
## What's New
### {Feature Name}
{1-2 sentence description of what the feature does and why it matters.}
**Highlights:**
- {Key capability 1}
- {Key capability 2}
## Enhancements
### {Enhancement Name}
{What improved and why it's better now.}
| Before | After |
|--------|-------|
| {Old behavior} | {New behavior} |
## Bug Fixes
| Issue | Fix | Impact |
|-------|-----|--------|
| {description} | {what was fixed} | {who is affected} |
## Known Issues
| Issue | Workaround | Expected Fix |
|-------|-----------|-------------|
| {description} | {workaround} | {target version} |
# Internal Release Notes — {version}
**Release Date:** {DD-MM-YYYY}
**Release Manager:** [your name]
**Deployment Type:** {Rolling / Blue-Green / Canary}
## Changes by Service
| Ticket | Type | Summary | Breaking? |
|--------|------|---------|-----------|
| {KEY-123} | Feature | {Summary} | No |
## Configuration Changes
| Config Key | Old Value | New Value | Service | Notes |
|-----------|-----------|-----------|---------|-------|
## Database Migrations
| Migration | Description | Reversible? | Duration |
|-----------|-------------|-------------|----------|
## Rollback Plan
{Steps to rollback if critical issues found}
## Monitoring Checklist
| Metric | Expected | Alert Threshold | Dashboard |
|--------|----------|-----------------|-----------|