npx claudepluginhub frank-luongt/faos-skills-marketplace --plugin faos-pmThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
Transform technical changelogs, PRs, and tickets into clear, user-facing release notes that communicate what changed and why it matters — in language customers understand.
Technical changelogs are written for developers. Release notes are written for customers. This skill bridges the gap — translating implementation details into benefit-oriented language that helps users understand, adopt, and appreciate product improvements.
Provide any combination of:
Sort every change into one of these categories:
| Category | Icon | Description |
|---|---|---|
| New Features | New | Entirely new capabilities |
| Improvements | Improved | Enhancements to existing features |
| Bug Fixes | Fixed | Issues that are now resolved |
| Breaking Changes | Breaking | Changes that require user action |
| Deprecations | Deprecated | Features being removed in a future release |
Transform each change from technical to user-facing:
Rules:
Examples:
| Technical (Before) | User-Facing (After) |
|---|---|
| Implemented Redis caching for dashboard queries | Dashboards now load up to 3x faster |
| Fixed null pointer exception in report export | Report exports no longer fail for accounts with empty custom fields |
| Added SAML SSO support (SCIM provisioning) | Enterprise teams can now sign in with their company SSO — no more separate passwords |
| Migrated search to Elasticsearch | Search results are now more accurate and return in under 200ms |
| Refactored payment processing module | (Omit — internal refactoring with no user-visible change) |
| Updated React from v17 to v18 | (Omit — unless there's a user-visible improvement) |
Adjust tone based on audience:
| Audience | Tone | Example |
|---|---|---|
| B2B Professional | Clear, confident, concise | "Dashboards now load up to 3x faster." |
| Consumer / Friendly | Warm, conversational, excited | "Your dashboards just got a speed boost — they load 3x faster now!" |
| Developer / API | Technical, precise, actionable | "Dashboard API response times reduced from ~900ms to ~300ms via query caching." |
# Release Notes — [Version or Date]
**Released:** [date]
---
## New Features
### [Feature Name]
[1-3 sentences describing what it does and why it matters to the user]
### [Feature Name]
[description]
---
## Improvements
- **[Area]** — [What improved and the benefit]
- **[Area]** — [What improved and the benefit]
---
## Bug Fixes
- Fixed an issue where [user-visible problem] — [what works now]
- Fixed an issue where [user-visible problem] — [what works now]
---
## Breaking Changes
### [Change Description]
**What changed:** [specific change]
**What you need to do:** [clear migration steps]
**Deadline:** [if applicable]
---
## Deprecations
- **[Feature/API]** will be removed on [date]. [Migration path or alternative].
Include:
Exclude:
Adapt the release notes for each channel:
| Channel | Format | Length |
|---|---|---|
| In-app notification | 1–3 bullet highlights | Very short |
| Email newsletter | Full release notes with context | Medium |
| Blog post | Narrative with screenshots | Long |
| App store description | Top 3 changes in bullet form | Very short |
| Changelog page | Full structured notes | Medium |
| Slack/Discord | Emoji-formatted highlights | Short |
| API docs | Technical details + migration guides | Technical |
| Avoid | Why | Instead |
|---|---|---|
| Ticket numbers in notes | Customers don't know what PROJ-1234 means | Describe the change in plain language |
| "Various bug fixes" | Dismissive, unhelpful, erodes trust | List specific fixes or say "stability improvements including [example]" |
| Technical jargon | "Optimized SQL query" means nothing to users | "Reports now load faster" |
| Listing internal refactors | Adds noise, no user value | Only include user-visible changes |
| No categorization | Hard to scan, important changes get buried | Use consistent categories |
| Stale release notes | Notes published days/weeks after release | Ship notes with the release |