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. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when p
Profile →npx skills add rampstackco/claude-skills --skill feature-launch-playbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill provides an operational playbook for launching features, covering positioning, internal alignment, customer communications, sales enablement, support readiness, rollout strategy, monitoring with rollback triggers, and post-launch measurement against hypotheses. It defines how to distinguish shipping, releasing, and launching, and offers tiered launch guidance (Tier 1 to Tier 3) to tailor the effort to feature scope. It also outlines pre-launch activities, launch-day rollout patterns, monitoring, and comms execution. It references specific pre-launch artifacts and templates for alignment, comms, enablement, and support readiness, and emphasizes measuring impact against predefined hypotheses.
How it works
- Establishes the difference between shipping, releasing, and launching to ensure proper discipline.
- Describes tiered launch approaches: Tier 1 (full launch), Tier 2 (focused launch), Tier 3 (release note).
- Outlines pre-launch phases: positioning, internal alignment, customer comms plan, sales enablement, and support readiness, each with defined inputs and outputs.
- Provides rollout strategy patterns and a monitoring framework with explicit rollback triggers before launch.
- Specifies launch-day execution where comms and rollout progress follow a calendar with owner responsibilities.
- Positions this skill as complementary to other PM discipline skills (spec-writing, roadmap planning, analytics, experiment design, feature flagging).
When to use it
- Planning a launch (any size, any segment).
- Auditing an existing launch process.
- Fixing the problem where a shipped feature did not move the metric.
- Building a launch checklist for the team.
What it can touch
- It references and integrates with processes and templates for internal alignment, customer comms, sales enablement, and support readiness. The skill relies on the existence of a feature flag/rollout infrastructure (feature-flagging) and instrumentation (product-analytics-setup) and testing (experiment-design).
Caveats
- Delivers a process-oriented playbook; does not cover pricing decisions, brand campaigns, or full GTM strategy. Requires collaboration with marketing for broader campaigns.
- Tiering guidance should be matched to feature characteristics to avoid comms fatigue or unlaunched releases.
# Feature Launch Playbook 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 read
What does the feature-launch-playbook skill do?
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. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when p
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill feature-launch-playbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.