pmm-feature-announcementlisted

# PMM Feature Announcement Release notes describe what changed. Feature announcements explain why anyone should care. ## Inputs - Product spec or release notes - Who benefits - What they can do now - Before state - After state - Announcement tier - Channels - Proof or early signal ## Workflow 1. Extract what matters - Capability - Before state - After state - Trigger moment - Magnitude 2. Classify announcement tier - Tier 1: marquee announcement - Tier 2: significant feature - Tier 3: incremental update 3. Find the narrative angle - The moment - The before/after - The unlock 4. Produce assets - Blog or changelog - Customer email - Social posts - In-product message - Sales or CS note - Optional image prompts ## Output Produce every section as **finished copy**, not a header with a sentence under it. Apply the PMM OS depth standard (see `../product-marketing-os/references/output-depth-standard.md` (and `pmm-content-writer` for word budgets)): each channel hits its budget, and the blog/changelog is real writing, not a stub. ### Depth budget per section | Section | Budget | | --- | --- | | Story extraction | the actual before/after + trigger + magnitude, in specifics — a named user type, the action they took, a number if you have one | | Blog or changelog copy | **700–1,200 words, 3–5 H2s, ≥1 concrete example, a clear CTA** — run it through the `pmm-content-writer` rubric. A pure changelog entry can be 150–300w but mu