Builds a dated pre-launch, launch-day and post-launch plan with every channel and asset given an owner and a due date, a dry run and buffer day, and the retro already scheduled.
Builds a dated pre-launch, launch-day and post-launch plan with every channel and asset given an owner and a due date, a dry run and buffer day, and the retro already scheduled. Use when planning a product launch end-to-end and you need the full dated timeline. Triggers on "plan my launch", "launch plan", "how do I sequence a launch", "pre-launch checklist", "what happens before launch day", "launch timeline", "GTM launch plan", "coordinate a launch across channels", "who owns what for launch". Builds the pre-launch → launch-day → post-launch arc with a channel & asset checklist, owners, and dates. Do NOT use when you need the minute-by-minute run-of-show for the day itself - use launch-day-runbook instead. Do NOT use to write the core message - use positioning-statement for the one-line claim and messaging-hierarchy for the laddered copy. Do NOT use to design the self-serve adoption motion - use plg-motion-designer. Do NOT use to build the sales deck, battlecard, or demo script - use sales-enablement-kit.This is the skill's description: the text your AI reads to decide when the skill applies.
launch-plan-sequencer/SKILL.md
---
name: Launch Plan Sequencer
description: Builds a dated pre-launch, launch-day and post-launch plan with every channel and asset given an owner and a due date, a dry run and buffer day, and the retro already scheduled. Use when planning a product launch end-to-end and you need the full dated timeline. Triggers on "plan my launch", "launch plan", "how do I sequence a launch", "pre-launch checklist", "what happens before launch day", "launch timeline", "GTM launch plan", "coordinate a launch across channels", "who owns what for launch". Builds the pre-launch → launch-day → post-launch arc with a channel & asset checklist, owners, and dates. Do NOT use when you need the minute-by-minute run-of-show for the day itself - use launch-day-runbook instead. Do NOT use to write the core message - use positioning-statement and messaging-hierarchy. Do NOT use to design the self-serve adoption motion - use plg-motion-designer. Do NOT use to build the sales deck, battlecard, or demo script - use sales-enablement-kit.
---
# Launch Plan Sequencer
A launch is not a day; it is an arc. The teams that botch launches treat "launch"
as a single deadline, pile every task onto it, and discover on the morning of that
the demo video is unrendered, sales has never seen the pitch, and nobody owns the
Hacker News thread. Your job is the opposite: stretch the launch into three phases -
**pre-launch**, **launch day**, **post-launch** - and assign every asset and
channel an owner and a date *before* the clock starts.
This skill owns the **sequence and the schedule**. It does not own the strategy
(what to launch, to whom, why now - that is a precondition the team brings in),
it does not own the message itself (that is [[positioning-statement]] and
[[messaging-hierarchy]]), and it does not own the minute-by-minute choreography
of the day itself (that is [[launch-day-runbook]]). You produce the map; those
skills fill in the territory.
## When to use this skill
Reach for it the moment someone says "we're launching" and there is no dated plan.
Run it once the strategy is settled and the message spine existsClick to play with sound.