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 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.
To provide a disciplined, step-by-step framework for ensuring features are not just shipped but successfully launched, maximizing their value capture and minimizing launch-related risks.
功能
- Defines clear launch tiers (1, 2, 3) to match effort to feature scope.
- Provides detailed templates for critical launch artifacts like positioning canvases and launch briefs.
- Outlines specific monitoring metrics, alert thresholds, and rollback triggers.
- Addresses common launch failure modes with diagnoses and prevention strategies.
- Emphasizes the distinction between shipping, releasing, and launching.
使用场景
- Planning and executing a Tier 1 or Tier 2 feature launch.
- Auditing an existing launch process to identify potential failure points.
- Building a standardized launch checklist for a product team.
- Diagnosing why a shipped feature failed to gain traction or move metrics.
非目标
- Defining the product specification or roadmap.
- Covering pricing decisions or brand campaign execution.
- Providing a generic template without opinionated guidance on best practices.
工作流
- Determine launch tier (1, 2, or 3).
- Define positioning: target user, problem, promise, proof points, anti-positioning.
- Align stakeholders internally via a launch brief.
- Plan customer communications across channels.
- Enable sales and support teams.
- Select and execute a rollout strategy.
- Define monitoring metrics and rollback triggers.
- Execute comms, gated by rollout health.
- Measure adoption, engagement, outcome, and side effects post-launch.
- Iterate based on post-launch analysis and feedback.
实践
- Product launch strategy
- Go-to-market planning
- Operational discipline
安装
npx skills add rampstackco/claude-skills通过 npx 运行 Vercel skills CLI(skills.sh)— 需要本地安装 Node.js,以及至少一个兼容 skills 的智能体(Claude Code、Cursor、Codex 等)。前提是仓库遵循 agentskills.io 格式。
质量评分
已验证类似扩展
Pm Gtm Launch
95Go-to-market launch playbook for a feature, module, or product. Generates cross-functional checklists, enablement timelines, communication plans, and success metrics. Scales from lightweight P2 launches to full P0 GTM motions. Use when someone says "launch plan", "go-to-market", "GTM", "launch playbook", "launch checklist", "feature launch", "product launch", "release planning", "launch readiness", or "launch brief".
International Expansion Strategy
100International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.
Incident Response
100Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.
Safe Mode
100Prevent destructive operations using Claude Code hooks. Three modes — cautious (warn on dangerous commands), lockdown (restrict edits to one directory), and clear (remove restrictions). Uses PreToolUse matchers for Bash, Edit, and Write.
Domain Strategy
100Plan, manage, and optimize a domain portfolio. Use this skill for DNS architecture decisions, redirect strategies, registrar choice, parking unused domains, multi-site setups, and domain consolidation or split planning. Triggers on DNS, domain, registrar, redirect, parking, subdomain, apex, www vs non-www, multi-site, portfolio, hreflang setup, domain migration. Also triggers when planning a new site that needs domain decisions made before launch.
After Action Report
100Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.