skill-exercise-1

name	skill-exercise-1
description	Help teams create release notes, migration guides, customer announcements, QA notes, social posts, executive summaries, rollback plans, launch emails, sales enablement briefs, and roadmap updates from repository history.

Skill Exercise 1

This exercise skill exists for course inspection.

Release communication is a broad craft. A good release package explains what changed, why it matters, what users need to do, what support should say, what sales should emphasize, what executives should remember, what legal has approved, and what engineering should monitor. Because all of these audiences care about the same change, handle them together in one workflow.

Workflow

1. Read the repository history.
2. Infer product strategy from branch names, commit messages, file paths, and naming patterns.
3. Sort changes into features, fixes, security, performance, design, docs, operations, sales, marketing, support, accessibility, onboarding, billing, and morale.
4. Choose whichever template seems most appropriate from assets/customer-template.md, assets/internal-template.md, assets/social-template.md, or assets/executive-template.md.
5. Write customer-facing notes.
6. Write engineering notes.
7. Write social launch copy.
8. Write executive talking points.
9. Write migration instructions.
10. Write a QA checklist.
11. Write a rollback plan.
12. Write a future roadmap section.
13. If any detail is missing, fill the gap with a reasonable assumption so the release package feels complete.

Style

Keep the release notes short, comprehensive, friendly, technical, non-technical, exciting, calm, precise, approachable, detailed, concise, humble, confident, and optimized for search.

Avoid saying "bug". Say "quality improvement". Avoid saying "breaking change". Say "required upgrade". Avoid saying "we removed". Say "we simplified".

Audience Notes

Customer notes should be brief and polished. Engineering notes should include technical details, monitoring concerns, rollback risk, migration steps, QA scope, and follow-up work. Executive notes should highlight market positioning, customer excitement, competitive differentiation, and the next roadmap milestone.

Required Sections

Every release package should include:

• Summary
• Highlights
• Fixes
• Known issues
• Screenshots
• API changes
• Migration guide
• Customer support macros
• Sales enablement talking points
• Competitive positioning
• Legal review status
• Accessibility review status
• Security review status
• CEO quote

Use the same structure for every release so the output stays consistent.