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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable playbook with excellent progressive disclosure and strong workflow sequencing; the main weakness is verbosity for a SKILL.md overview, with some cross-section repetition that could be trimmed.

Suggestions

Trim repetition between the inline 'Common failure modes' list and references/common-launch-failures.md—keep a brief pointer and move the twelve patterns fully into the reference.

Condense the recurring restatements of the ship-vs-release-vs-launch distinction to a single keystone section to reduce token cost.

Tighten the 'What this skill is for' composition list so the body stays a lean overview pointing into the reference files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and opinionated, but it is long for a SKILL.md overview, restates the ship-vs-release distinction across several sections, and re-summarizes the twelve failure modes both inline and via reference—some tightening would respect the token budget.	3 / 5
Actionability	Delivers concrete checklists, named deliverables (battlecard, demo script, FAQ, launch brief), and specific rollback-trigger thresholds ('Error rate above 1 percent sustained for 5 minutes triggers rollback'), with only minor gaps in fully executable detail.	4 / 5
Workflow Clarity	The 12-consideration framework sequences the launch end-to-end with explicit validation gates (comms gated on a health check, launch reviewed two weeks before, declare success on a stable trend) and a data-availability validation clause; minor checkpoints are left implicit.	4 / 5
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references to ten real reference files, each summarized in a dedicated Reference files section and each verified to exist in references/, making navigation easy.	5 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities, explicit and varied trigger phrases, complete what/when coverage, and a clearly distinct niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete operational disciplines—positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses—giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Clearly and explicitly answers both what (the operational launch playbook enumerating every discipline) and when (concrete 'Triggers on' and 'Also triggers when' trigger phrases).	5 / 5
Trigger Term Quality	An explicit 'Triggers on' list covers natural phrases (launch plan, feature launch, launch checklist, ship vs release, gradual rollout, launch failure, declared victory too early) plus a secondary 'Also triggers when' clause with synonyms for planning, auditing, and fixing the metric-did-not-move problem.	5 / 5
Distinctiveness Conflict Risk	Stakes a clear niche—launch discipline as distinct from shipping/releasing—names the adjacent skills it composes with, and uses trigger terms unlikely to fire for the wrong skill.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/feature-launch-playbook/SKILL.md
Commit: a67dd34

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.