| name | momentum-planner |
| slug | aaron-momentum-planner |
| displayName | Momentum Planner · 发布势能延续 |
| summary | 抗第二周断崖/changelog-as-GTM/relaunch/下一时刻 |
| description | Use when the user asks to "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", or "is this update worth a relaunch"; produces a T+1→T+30 momentum plan — a launch-moment calendar (milestone / shipped-loop / badge moments only), announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only), a relaunch legitimacy call, spike-to-owned handoff briefs, and the next Tier-1 moment with launch-stacking spacing. Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner. 抗第二周断崖/changelog-as-GTM/relaunch/下一发布时刻 |
| version | 19.2.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when a launch spike is fading and the T+1 to T+30 window needs planned launch moments: milestone announcements, shipped-loop release moments, badge / award moments, a changelog or release-notes-as-GTM cadence, a relaunch legitimacy call, or picking and spacing the next Tier-1 moment against the launch calendar. The moment-scheduling layer above content repurposing (content-amplifier) and below the next full launch plan (launch-tier-planner). |
| argument-hint | <launch slug / spike data> [window: T+1→T+30] [candidate next moments] |
| metadata | {"author":"aaron-he-zhu","version":"19.2.0","discipline":"launch","phase":"prove","geo-relevance":"low","hermes":{"tags":["marketing","launch","prove"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
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 RAMP profile result (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?
Skill Contract
Expected output: a T+1→T+30 momentum plan — a dated launch-moment calendar with each moment classified (milestone / shipped-loop / badge), an announcement-tier routing rule for the changelog cadence, a relaunch legitimacy call, spike-to-owned handoff briefs addressed to their owning skills, the next Tier-1 moment candidate with its spacing check, and the standard handoff summary.
