Menu

Individual skill

momentum-planner

0upvotes

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/下一发布时刻

launch/prove/momentum-planner/SKILL.md

Read pinned source

Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,135
Repository last updated
Nov 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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](../../../references/ramp-benchmark.md) 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](../../../influencer/activate/content-amplifier/SKILL.md) — 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](../../research/launch-tier-planner/SKILL.md)), does not build the owned assets it briefs ([page-play-builder](../../../seo-geo/implement/page-play-builder/SKILL.md), [content-writer](../../../seo-geo/implement/content-writer/SKILL.md), [list-growth-designer](../../../email/setup/list-growth-designer/SKILL.md)), does not write `memory/launch-registry/` ([launch-registry](../../../protocol/launch-registry/SKILL.md) is the sole writer — this skill submits candidates), and does not score the RAMP profile result ([launch-readiness-auditor](../../mobilize/launch-readiness-auditor/SKILL.md)).

## 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?
Back to top