Ship the launch with assets done and owners named.
Builds a tiered go-to-market launch plan sized to what the release actually deserves.
Inside: The tiering, the audiences, channel-to-asset mapping, a back-planned timeline, and win metrics.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it sizes real audience segments and picks the channels that reached them last time.
it sets baseline metrics from your real traffic, so the win condition is grounded, not guessed.
it can slot the assets into a real publishing calendar instead of a static list.
This was built for a B2B product team shipping features and products. Set these to your stack:
Pick the tier honestly. A T3 feature dressed as a T1 launch burns the team and the audience's attention. The skill recommends a tier and tells you why.
| Set this | What it is | Example |
|---|---|---|
| WHAT | the thing you are launching | a featurea producta rebrand |
| TIER | the size of the push | T1 majorT2 standardT3 minor |
| AUDIENCES | who needs to hear it | existing usersprospectspress |
| CHANNELS | where you will reach them | emailblogsocialin-appsales |
| CRM | your audience-data connector | a CRMa marketing tool |
| ANALYTICS | your web-analytics connector | a web-analytics tool |
| LEAD_TIME | days from kickoff to launch | 14 (re-tune to the tier) |
Everything the skill does, in full.
Turns "we are shipping something" into a plan someone can run. It sizes the launch to a tier, then fills in the audiences to reach, the channels to reach them, the assets each channel needs, a timeline with a real launch day, the owner for every piece, and the handful of metrics that decide whether it worked. No orphaned tasks, no launch day where the assets are not done.
- 1Tier the launch (T1 / T2 / T3)
First decision, everything follows from it. T1 is a major bet: full channel push, sales enablement, press. T2 is a standard feature: email, blog, social, in-app. T3 is a minor update: changelog and one in-app note. The skill recommends a tier from WHAT and lets you override.
- 2Audiences
Names who needs to hear it, in priority order: existing users who benefit today, prospects it unblocks, and internal teams (sales, support) who field the questions. Real segment sizes when a CRM is connected, named segments when not.
- 3Channels and assets
Maps each audience to the channels that reach them, and each channel to the exact asset it needs: the email, the blog post, the social thread, the in-app note, the sales one-pager. Every asset has a channel and every channel has an audience. Nothing floats.
- 4Timeline and owners
Back-plans from launch day across LEAD_TIME: asset drafts, reviews, a go or no-go, launch, and follow-up. Every item has a named owner. An unowned task is flagged before it becomes a launch-day surprise.
- 5Win metrics
Two or three metrics that decide success, matched to the tier and the goal: adoption of the feature, signups from the campaign, pipeline influenced. Baselines come from a connected analytics tool, or are labeled "set a baseline" when none is connected. A launch with no win condition is just noise.
- Every asset has a channel, an owner, and a due date before launch day. No orphans.
- The tier is stated and justified. A T3 does not get a T1 budget.
- Win metrics are named up front, with a baseline or a clear "set a baseline" flag.
- Illustrative audience sizes and metric targets are marked as examples, never presented as your real data.
LAUNCH PLAN · shipping: bulk-export feature · recommended tier: T2 Audiences (priority): 1. Existing power users (benefit today) 2. Prospects who asked for export 3. Support + sales (will field questions) Channels -> assets -> owner -> due: Email release note to power users PMM L-2 Blog how-to with screenshots PMM L-3 In-app tooltip on the export button PM L-1 Social 3-post thread PMM L-day Sales one-pager + talk track PMM L-2 Timeline (LEAD_TIME 14): L-14 kickoff -> L-5 drafts done -> L-2 review + go/no-go -> L-day ship -> L+7 follow-up post Win metrics (T2): - Feature adoption among power users (set a baseline) - Export-related tickets down (set a baseline) Next: connect a CRM to size the power-user segment for real.
Where an operator takes this next.
The plan is step one. Here is where an operator takes it once the manual version proves out.
You built the plan once, now the system tracks whether it worked.
Sync the owner-and-due list into Linear or Asana so L-2 and L-3 deadlines show up where the team already works, not just in this doc.
Connect Salesforce or HubSpot so "existing power users" becomes an actual count instead of a named-but-unsized audience.
Run a scheduled Claude task at L+14 that pulls the win metrics from Amplitude and reports whether the launch actually hit, so the next tier call is calibrated on results, not gut feel.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.