product-launch-manager — Claude Code skill: what it does
product-launch-manager runs a product launch as a staged plan: tier, timeline, RACI, beta, go/no-go and a retrospective. Useful when a release needs a checklist rather than hope.
no license 173 installs ★ 54 updated 2026-02-26
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a claude-codeWhat product-launch-manager does
The skill hands the agent a launch playbook. Releases get sorted into four tiers, from a new product with a full press push and an 8-12 week runway down to a UI tweak that only needs a changelog line and 1-2 weeks. A readiness model then pulls product, marketing, sales and support into a single go/no-go point, and a RACI chart spells out who owns each line.
Everything lives as rules under rules/, split by prefix: planning-* covers strategy and dates, coordination-* covers team alignment, beta-* covers early access, with communication, launch day and post-launch in their own groups. Templates come along too: a launch brief outline, a go/no-go checklist, and a timeline running from week -8 to week +2.
It writes plans, not code. Nothing here ships a build or flips a flag, so the answers still have to come from your team. Tier 1 in this model means 8-12 weeks, which is why a release two weeks out lands in a lower tier whether you like it or not. The anti-pattern list is the blunt part: no tiers at all, walking away once the announcement goes out, success criteria invented after the numbers are in.
What it helps with
- sort a release into a launch tier with a matching timeline
- build a RACI chart across product, marketing, sales and support
- run a beta cohort and close the feedback loop
- clear a go/no-go check before launch day
- review launch metrics in a retrospective
Example prompts for the agent
- Plan the launch of our new integration: pick the tier, set the timeline, name owners
- Draft a go/no-go checklist covering product, marketing, sales and support
- Write the retrospective for the launch we just finished and tell me which metrics mattered
How to install product-launch-manager
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a claude-code2Manually: put the files in place
~/.claude/skills/product-launch-manager/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-launch-manager/
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a codex2Manually: put the files in place
.agents/skills/product-launch-manager/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a cursor2Manually: put the files in place
.cursor/skills/product-launch-manager/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ncklrs/startup-os-skills skills/product-launch-manager2Manually: put the files in place
.github/skills/product-launch-manager/SKILL.md1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a gemini-cli2Platform CLI
gemini skills install https://github.com/ncklrs/startup-os-skills --path skills/product-launch-managerManually: put the files in place
.devin/skills/product-launch-manager/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-launch-manager
How do I install product-launch-manager in Claude Code?
Run npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a claude-code. The skill file lands at ~/.claude/skills/product-launch-manager/SKILL.md.
What does product-launch-manager do?
It plans a release end to end: tier and timeline, a RACI split, a beta program, the go/no-go gate and a retrospective built on metrics.
What does the go/no-go checklist cover?
Product and engineering readiness, a documented rollback plan, monitoring and alerts, marketing content, sales enablement, support docs, legal review and final exec approval.