Skip to content
Skills Library
Marketing & content · Planning

launch-plan

/launch-plan

Builds a full campaign or launch plan working backwards from a hard date — the big idea, the complete asset list with deadlines, the T-minus timeline, channel-by-channel choreography, and mid-launch decision triggers agreed before emotions are involved. Use when launching a product, offer, or campaign and the date is real.

Licence
MIT
Last repository change
08.07.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Builds a full campaign or launch plan working backwards from a hard date — the big idea, the complete asset list with deadlines, the T-minus timeline, channel-by-channel choreography, and mid-launch decision triggers agreed before emotions are involved. Use when launching a product, offer, or campaign and the date is real.

Arguments

/launch-plan [what is launching + the date + the number it must hit]
Original author description

Builds a full campaign or launch plan working backwards from a hard date — the big idea, the complete asset list with deadlines, the T-minus timeline, channel-by-channel choreography, and mid-launch decision triggers agreed before emotions are involved. Use when launching a product, offer, or campaign and the date is real.

How it works

  1. Inputs
  2. Do this
  3. Output
  4. Rules
Original SKILL.md headings · 31 lines, 544 words
SKILL.md preview
---
name: launch-plan
description: Builds a full campaign or launch plan working backwards from a hard date — the big idea, the complete asset list with deadlines, the T-minus timeline, channel-by-channel choreography, and mid-launch decision triggers agreed before emotions are involved. Use when launching a product, offer, or campaign and the date is real.
argument-hint: "[what is launching + the date + the number it must hit]"
---

# Launch Plan — work back from the date, decide plan B now

Launches fail in predictable ways: assets finish late, every channel fires the same generic announcement, and mid-launch panic produces day-3 decisions that should have been made in week minus-3. This plan works backwards from the date, gives every channel its native role, and writes the plan-B triggers while nobody is panicking.

## Inputs
- What is launching, the hard date, and the one number the launch must hit: $ARGUMENTS
- From `marketing-brief.md` if present: top pains and desires (the big idea comes from them), the offer, the primary channel, the message pillars, and the language bank for copy.

## Do this
1. Fix the goal and the date. One number the launch must hit — revenue, signups, booked calls — and the date it must hit it by. Everything else flexes; these two do not.
2. Choose the big idea: the one angle or story the whole campaign hangs on, drawn from the sharpest pain or desire in the brief. Test it in one sentence — would the ICP stop for it? A launch with three big ideas has none.
3. Write the asset list — landing page, email sequence, posts, ads, creative, sales enablement — each tagged with the funnel stage it serves and the pillar it ladders to. Inside Claude Code, the launch-planner agent runs the deep version of this pass, and asset builds route to the creative skills (`/marketing:hook-factory` for the openers, for instance).
4. Build the T-minus timeline backwards from launch day: assets locked, warm-up and seeding phase (the audience should feel it coming), open day, mid-launch proof drop, close sequence. Every item gets a deadline and an owner, even if every owner is the same person.
5. Choreograph the channels — what fires where, when, in what order, each in its native role rather than reposting the same announcement:
   - Long-form and email carry the argument and do the closing.
   - Social builds surround-sound presence and pulls people into the argument.
   - The primary channel carries the weight; everything else exists to feed it.
6. Pre-agree the mid-launch decisions: the day-2 or day-3 numbers that trigger plan B — swap the angle, drop more proof early, extend the close, or hold steady. Written now, not improvised on day 3.
7. Name the two most likely failure points and the pre-built response to each.

## Output
The one-page launch plan — goal and date, big idea, asset list with deadlines and owners, T-minus timeline, channel choreography grid, decision triggers, and the risk pass. After the launch, run `/marketing:campaign-debrief` to bank what it taught.

## Rules
- The date is fixed; scope flexes. Cut assets before cutting the deadline — a smaller launch on time beats a fuller one late.
- One big idea. Every asset is a variation on it, or it gets cut.
- Plan the close hardest. Most launch revenue arrives at the end, and the close sequence is the worst place to improvise.
- Never launch cold. The warm-up phase is part of the launch, not overhead to trim.
- Real urgency only. If there is no genuine reason to act now, build one into the offer before launching, or launch without a countdown.

Versions

RepositoryScoreLicence
This page · styfinity/claude-marketing-department90MIT
tansuasici/claude-marketing-kit100MIT
calven-ai/marketing-as-code100MIT
SimonFoote-greensparx/CopilotForge100CC-BY-4.0
Sidsaladi9/persona-os100MIT
karix-ai/launch-skills90MIT
devsolanki001/product-launch90MIT

Database snapshot: 13.11.2026 · package version e3ff18db1741 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100marketing-launch-plan
    Plans a product or feature launch across channels with a pre-registered metric stack, asset list, timeline (pre-launch, launch day, sustain), and per-channel owners. Pulled by the `marketing` specialist. TRIGGER: "plan the launch for <feature>", "draft the GTM launch plan",…
  • 100fai-gtm-launch
    Execute a go-to-market launch plan for an AI product — messaging, channel sequencing, launch-day checklist, and post-launch metrics. Use this skill when shipping a launch, coordinating announcements, or planning launch timing — even if the user only says "we're launching" or "launch plan".
  • 100launch-planning
    Plan product and feature launches across owned, earned, community, partner, and outbound channels. Produces launch narrative, audience map, asset checklist, channel calendar, risk plan, and measurement dashboard. Use when launching a startup, feature, campaign, Product Hunt…
  • 10041-campaign-asset-list-global
    Use when a campaign needs its full design asset list before anyone opens a tool — asset type, dimensions, channel, quantity, priority, owner, deadline, and status, with deadlines counted backward from launch day on a T-14 to D+1 timeline plus a naming convention. Trigger on…
  • 100launch-campaign
    Plan and run a B2B product or feature launch - launch surface (first screen, demo, signup path), channel plan across founder and brand social, email, communities, launch platforms and review directories, a T-7 to T+1 timeline, comment response plan, one primary metric with two…
  • 90app-launch
    When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.