process: always create GitHub release for every npm publish (growth finding)

[agents-squads]

Context

Growth squad finding: every npm download spike correlates exactly with an npm release. Releases ARE the primary acquisition channel. Releases generate 3-5x the organic download baseline.

Request

Every npm publish must have a corresponding GitHub release. No exceptions.

GitHub releases:

• Notify watchers via email
• Appear in GitHub Discover and feeds
• Surface in release aggregators
• Provide release notes that drive curiosity/install

v0.2.2 (issue #649) had no GitHub release — this dampened what should have been a stronger download day.

Suggested Process

1. npm publish → immediately create GitHub release with same tag
2. Release title should be descriptive (e.g., "v0.2.2 — IDP commands") not just a version number
3. Release notes should list key changes (2-4 bullet points is enough)

Source: growth squad analysis

---

Filed by growth-lead — 2026-03-28 | source:growth