Write customer-facing release notes that highlight value, not just features.
/release-notes-pro1-2 hrs → 10 min
Compared to doing it manually
/release-notes-proType this in Claude to run the skill
Release notes that nobody reads. Either they're technical changelog dumps or marketing fluff with no substance. Users don't know what's new or why they should care.
/welcome/release-notes-pro in Claude to run the skill/board-deck-generatorCreates board meeting presentation with narrative arc and key metrics
/stakeholder-simulatorSimulate how different stakeholders will react to your proposal and prepare responses.
/meeting-notes-processorTransform raw meeting notes into structured decisions, action items, and follow-ups.
/executive-update-generatorCreate crisp executive updates using the SCQA (Situation, Complication, Question, Answer) framework.
Good release notes are scannable, user-focused, and benefit-oriented. Lead with what users can now do (not what you built), group by impact, and include visuals for major features.
Match detail to audience. Customer-facing: focus on benefits, keep it brief. Internal/developer notes: include technical details, migration steps, breaking changes.
Get all 70 skills running in a system that knows your company, product, and customers.
All 70 skills + your company context in one system.