Momentum Planner

Fights the second-week cliff after a launch. Most launches lose the bulk of their spike traffic within days; this skill plans the T+1→T+30 window as a calendar of launch moments — milestone announcements, shipped-loop release moments, badge / award moments — sets the changelog / release-notes-as-GTM cadence, judges when a ship is a legitimate relaunch moment, routes the spike into owned assets, and books the next Tier-1 moment at a sane distance from the last one. It sits in the Prove phase of the RAMP loop and feeds the P momentum / next-moment sub-item; the spacing facts it produces are the upstream of the M launch-stacking guardrail. It works one lever — momentum — and hands off.

Scope guard: this skill schedules moments only. The 30-day content-reuse map and the paid amplification execution calendar belong to content-amplifier — this skill decides when a moment happens, content-amplifier decides how its content gets distributed. It does not plan the next launch end to end (launch-tier-planner), does not build the owned assets it briefs (page-play-builder, content-writer, list-growth-designer), does not write memory/launch-registry/ (launch-registry is the sole writer — this skill submits candidates), and does not score the LQS (launch-readiness-auditor).

Quick Start

Plan the T+1→T+30 momentum window for [launch]. Launch-week spike: [traffic/signups]. Week 2 so far: [numbers].

We ship weekly — set a changelog / release-notes-as-GTM cadence for [product]. Which upcoming releases deserve an announcement?

We launched [product] months ago and just shipped [feature]. Is that a legitimate relaunch moment, and when is the next Tier-1 slot?