| name | changelog-marketing |
| description | Decide whether a changelog entry should stand alone or batch with others, run the quality gate, and produce a publish-ready entry with SEO title and visual recommendation. |
| triggers | ["changelog","release notes as content","changelog SEO","changelog entry","what to include in changelog","changelog vs announcement post"] |
| role | growth |
| layer | growth |
| version | 0.1.0 |
| sources | ["Linear changelog methodology — Linear (public, 2022–2024)","Reforge Growth Series — Reforge (2023)","aether-launch-copilot knowledge base — aether (2026)"] |
| borrowed_from | null |
Changelog Marketing
Purpose
Turns a product changelog from an internal record into a compounding SEO and community asset. Decides whether a release warrants a standalone entry, a batched summary, or a full announcement blog post. Runs a quality gate before publish to catch weak entries that damage changelog credibility.
Built for PMMs and DevRel leads who want to extract ongoing traffic value from release cadence without over-announcing small changes.
Inputs
| Input | Required? | Description |
|---|
| Release description | Required | What shipped — feature name, change summary, user-facing impact |
| Release type | Required | Major / minor / patch / internal |
| Target persona | Required | Who uses this feature |
| Prior changelog publish date | Optional | When the last entry was published — informs batching decision |
| SEO context | Optional | Target keywords from content strategy |
| Visual assets available | Optional | Screenshots, GIFs, or architecture diagrams available for the entry |
| Brain context | Optional | Prior changelog performance data |
Brain read (if connected):
brain/read: changelog_performance_history, seo_keyword_targets
Outputs
| Output | Format | Description |
|---|
| Publish decision | Markdown decision record | Standalone / batched / blog-post with rationale |
| Quality gate result | Checklist | Pass / fail per quality criterion |
| Changelog entry | Markdown | 80–150 word entry with SEO title and visual recommendation |
Brain write (if connected):
brain/write: changelog_entry_published, seo_title, visual_type
Decision Logic
Step 1 — Publish decision
IF release_type = major OR feature_impact = high
THEN: Standalone entry. Consider full announcement blog post if metrics justify.
IF release_type = minor AND days_since_last_entry < 7
THEN: Batch. Accumulate until 7-day threshold OR 3+ minor entries, then publish batch.
IF release_type = patch OR change is internal/infrastructure
THEN: Skip public changelog. Internal record only.
IF release includes a breaking change
THEN: Standalone entry REQUIRED. Flag for migration guide link.
