Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add rampstackco/claude-skills-pm --skill feature-launch-playbookgit clone --depth 1 https://github.com/rampstackco/claude-skills-pmWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rampstackco/claude-skills-pm/feature-launch-playbook)<a href="https://agentmods.dev/skills/rampstackco/claude-skills-pm/feature-launch-playbook"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills-pm/feature-launch-playbook/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rampstackco/claude-skills-pm/feature-launch-playbook"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills-pm/feature-launch-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00146 | $0.05337 |
| Opus 5 | $0.00073 | $0.02669 |
| Sonnet 5 | $0.00029 | $0.01067 |
| Haiku 4.5 | $0.00015 | $0.00534 |
Grade A, and why
feature-launch-playbook scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
97% identical to feature-launch-playbook — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 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.
What this skill is for
This skill spans the operational launch discipline. It composes with the rest of the Product skill suite.
pm-spec-writingdefines the launch hypotheses; this skill validates them.roadmap-planningprovides the launch context (what came before, what comes next).product-analytics-setupis the instrumentation prerequisite; without it you cannot measure the launch.experiment-designanddata-warehouse-experimentationprovide the methodology for testing whether the launch worked.feature-flaggingprovides the rollout infrastructure this skill depends on.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/common-launch-failures.md 11 KB
- references/customer-comms-playbook.md 7.9 KB
- references/internal-alignment-checklist.md 7.2 KB
- references/launch-tier-decision.md 6.8 KB
- references/monitoring-readiness-checklist.md 8.2 KB
- references/positioning-canvas.md 8.3 KB
- references/post-launch-measurement-framework.md 9.2 KB
- references/rollout-strategy-patterns.md 8.8 KB
- references/sales-enablement-template.md 8.1 KB
- references/support-readiness-checklist.md 7.5 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 341 lines · 146 tokens per session scan A c3d0d12ac22d
feature-launch-playbook is a skill published in the GitHub repository rampstackco/claude-skills-pm (4 stars, last pushed 1mo ago), licensed MIT. It adds 146 tokens to every session and 5,337 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to feature-launch-playbook, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.