What problem does it solve? Turning a shipped work window into release notes often degrades into pasting a changelog or commit log into a doc, leaving customers without a clear picture of what they can now do and teams without a traceable record of what shipped. This Skill provides the discipline for both cuts from the same shipped-window truth. ## Core Features & Use Cases - Customer-facing notes: Lead with user benefit, group items by theme, call out behavior changes affecting existing workflows, and link to docs; written to .hero/planning/release-notes/<window-or-tag>/customer.md. - Internal updates: Keep spec slugs, name owners, and link each shipped item back to its originating PRD or initiative; written to .hero/planning/release-notes/<window>/internal.md. - Shipped-status verification: Pulls what shipped from the graph (spec status is completed plus an engineering close-out in owner_history), surfacing orphan deliveries instead of including them. - Use Case: After a release window closes, ask for the week's release notes and receive a themed, benefit-led customer announcement plus an internal traceable record of who shipped what and why. ## Quick Start Ask the agent to draft release notes for everything shipped this week, producing both the customer-facing and internal versions.
