Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rampstackco/feature-launch-playbook
The operational playbook for launching a feature well. Positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses, and the discipline that distinguishes shipping from releasing from actually launching.
Passed 16 of 22 test cases with the skill, and 5 of 22 without it.
and 14 more in the full report
11 fixed5 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Review our launch positioning draft for a new API key manager: Target User: Developers; Problem: Managing keys is slow; Promise: Manage keys in 1 click; Proof: Instant key revocation. Which two required positioning sections were left out?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies current alternatives as a missing positioning section. | Passed | Passed |
| Identifies anti-positioning as a missing positioning section. | Missed | Passed |
The instructions your model reads when the skill loads.
A veteran PM-leader's playbook for launching features well, not just shipping them.
Most teams conflate shipping, releasing, and launching. Shipping means engineering work is complete. Releasing means users can access it, even if it is behind a flag at 1 percent. Launching is the discipline of positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring, and post-launch measurement that turns "feature exists" into "feature lands."
A feature that ships without launching costs you the same engineering investment but captures a fraction of the value. Sales does not know how to sell it. Support does not know how to help with it. Customers do not notice it. The metric you said you would move does not move because nobody knows the feature is there.
This skill is the operational playbook. It assumes you have already written the spec (pm-spec-writing), prioritized it onto the roadmap (roadmap-planning), instrumented it (product-analytics-setup), and possibly tested it (experiment-design). The launch is the next discipline: how to actually get the feature in front of the right users, with the right context, in a way that lets you measure whether it worked.
When to use this skill: planning a launch (any size, any segment), auditing an existing launch process, fixing the "we shipped it but the metric did not move" problem, or building a launch checklist for the team.
This skill spans the operational launch discipline. It composes with the rest of the Product skill suite.
pm-spec-writing defines the launch hypotheses; this skill validates them.roadmap-planning provides the launch context (what came before, what comes next).product-analytics-setup is the instrumentation prerequisite; without it you cannot measure the launch.experiment-design and data-warehouse-experimentation provide the methodology for testing whether the launch worked.feature-flagging provides the rollout infrastructure this skill depends on.This skill does not cover pricing decisions, brand campaigns, or full GTM strategy. Those need a marketing team partner; this is the PM operational playbook for the engineering and product side.
The audience is broad: every PM ships features, every PM has launched poorly at least once, every PM benefits from a checklist that stops the worst failure modes from recurring. The voice is veteran PM-leader to PM. Specific, opinionated, honest about what discipline matters at what stage.
The keystone distinction. Three definitions.
Shipping means engineering completes the work. Code is on production. No users can access it yet, or only internal users via a flag. The PR is merged and deployed.
Releasing means users can access it. Could be 1 percent rollout, could be 100 percent. The feature is "live" in some technical sense. The flag is on for at least one user.
Launching means positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring, and post-launch measurement are all in flight. The feature has been introduced to the people who would benefit from it, with the context they need to use it.
test cases passed, vs 5 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.