Release Notes Skill

Produces professional, stakeholder-ready release notes from git history. The audience is non-technical: product owners, executives, clients, or QA leads. The output must contain zero technical jargon, zero commit hashes, zero internal identifiers — only user-facing value, business impact, and honest transparency.

Project context (fixed — do not ask the user):

• Platform: Android only
• Technology: Flutter

Read references/writing-guide.md before writing any content.
Read references/templates.md to select and fill the right template.
Read references/mermaid-flows.md before deciding whether to include visual flow diagrams.

Step 1 — Gather context

Before touching git, collect the following. Infer from context when possible; ask only for what's missing: