Menu

Individual skill

launch-plan-sequencer

0upvotes

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.

skills/launch-plan-sequencer/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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)
24
Repository last updated
Oct 13, 2026
License
MIT

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

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

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