agentsclimarketplace
Sign in

Launch planning

Skill Dragoon0x/product-skills/skills/execution-discipline/launch-planning

Plan and execute product launches that actually drive adoption, not just announcements. Covers launch tiers, cross-functional coordination, rollout strategy, and post-launch monitoring. Use when preparing a feature or product launch, coordinating across teams, or when past launches haven't moved the needle.From its SKILL.md

Install
npx -y skills add Dragoon0x/product-skills --skill launch-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 466 tokens by cl100k_base, as published. Nobody here has run it

Launch Planning

Plan launches that drive adoption, not just press releases.

How to use

  • /launch-planning Apply launch planning constraints to this conversation.
  • /launch-planning <feature> Build a launch plan for the described feature or product.

Constraints

Launch Tiers

Not every launch deserves the same effort. Tier them:

  • Tier 1 (big deal): new product, major feature, pricing change. Full cross-functional coordination.
  • Tier 2 (notable): significant improvement, new integration. Blog post, email, in-app announcement.
  • Tier 3 (incremental): bug fixes, small improvements. Changelog entry, maybe a tooltip.
  • MUST assign a tier before planning. Over-launching small things causes announcement fatigue.

Pre-Launch

  • MUST define success metrics before launch, not after
  • MUST have a rollout plan: internal dogfood → beta → phased → GA
  • SHOULD run through the launch checklist with every function: engineering, design, marketing, sales, support
  • MUST ensure support and sales know about the launch before customers do
  • NEVER launch without documentation and support readiness

Launch Day

  • MUST have a single owner for launch coordination
  • SHOULD have a war room or dedicated channel for real-time issue tracking
  • MUST monitor key metrics in real time during rollout
  • MUST have a rollback plan if something goes wrong
  • NEVER launch on a Friday unless you want to work the weekend

Post-Launch

  • MUST review metrics against success criteria within 1-2 weeks
  • SHOULD gather early user feedback actively, not passively
  • MUST run a retrospective: what went well, what didn't, what to change next time
  • SHOULD have a fast-follow plan for known gaps and quick improvements
  • NEVER move on immediately without measuring whether the launch actually worked

Anti-Patterns

  • The Silent Ship: launching without telling anyone and wondering why adoption is low
  • Launch and Forget: big announcement, zero follow-through or measurement
  • The Big Bang: months of secret building followed by a massive reveal. Ship incrementally instead.
  • Support Surprise: customers asking about a feature support hasn't heard of
  • The Premature Launch: announcing before the product is actually ready to handle real usage

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.