momentum-planner

Plans a T+1 to T+30 launch-moment calendar with changelog cadence and relaunch legitimacy checks.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/qaz26688442/bo-car --skill momentum-planner-qaz26688442
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: momentum-planner
Source: https://github.com/qaz26688442/bo-car/tree/main/.agents/skills/momentum-planner
Command: npx skills add https://github.com/qaz26688442/bo-car --skill momentum-planner-qaz26688442

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Most launches lose the bulk of their spike traffic within days, and teams have no plan for the second week onward. This Skill turns the T+1 to T+30 post-launch window into a dated calendar of launch moments so the spike converts into sustained momentum instead of a cliff. ## Core Features & Use Cases - Launch-Moment Calendar: Builds a dated T+1 to T+30 schedule of milestone announcements, shipped-loop release moments, and badge or award moments, explicitly excluding content-distribution slots. - Changelog-as-GTM Cadence: Routes each upcoming release through announcement tiers (major = full-channel, medium = targeted, minor = changelog-only) so minor ships never burn full-channel attention. - Relaunch Legitimacy & Next Tier-1 Moment: Judges whether a new ship qualifies as a genuine relaunch moment, checks spacing against the last Tier-1 moment in the launch calendar, and hands spike-to-owned briefs to page, content, and email skills. - Use Case: After a Product Hunt launch fades, ask for a momentum plan and receive a dated moment calendar, a release-announcement tiering rule, a relaunch verdict, and the next Tier-1 candidate with a spacing check. ## Quick Start Plan the T+1 to T+30 momentum window for my launch, given the launch-week spike numbers and this week's traffic so far.

Frequently Asked Questions about momentum-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep launch momentum going after launch week?▼

Plan the T+1 to T+30 window as a calendar of dated launch moments: milestone announcements, shipped-loop release moments, and badge or award moments. This Skill builds that calendar from your spike-decay data and roadmap, then books the next Tier-1 moment with a spacing check.

How do I use a changelog or release notes as a GTM channel?▼

Route each upcoming release through announcement tiers: major releases get a full-channel moment, medium ones get a targeted announcement, and minor ones stay changelog-only. Default to the smaller tier when unsure so minor ships never consume full-channel attention.

When does a new feature count as a legitimate relaunch?▼

A ship is a new launch moment only when it changes what the product is for someone: a material new capability, a new audience, or a real stage change like beta to GA. Re-posting the same product is not a moment, and platform re-submission rules come from each platform's official policy pages.

What is the difference between momentum-planner and content-amplifier?▼

Momentum-planner decides when launch moments happen and schedules them on the T+1 to T+30 calendar. Content-amplifier owns the 30-day content-reuse map and paid amplification execution, deciding how each moment's content gets distributed.

What data does the momentum plan need as input?▼

It needs launch-week spike and current-week decay numbers from your own analytics export or user-provided figures, plus the shipping roadmap or changelog backlog. Spacing and stage facts come from the launch-registry calendar; if no calendar record exists, the spacing check is marked NEEDS_INPUT.

What are the limitations of the momentum-planner skill?▼

It schedules moments only: it does not build the 30-day content-reuse map, plan the next launch end to end, build owned assets, or write the launch registry directly. It submits moment and claim candidates via propose operations for launch-registry to formalize.