# product-launch-manager

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 173 installs · ★ 54 repo stars
- Author: ncklrs
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ncklrs/startup-os-skills/tree/HEAD/skills/product-launch-manager/SKILL.md
- Updated: 2026-02-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/product-launch-manager

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/product-launch-manager/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/product-launch-manager/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/product-launch-manager/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/product-launch-manager/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install ncklrs/startup-os-skills skills/product-launch-manager
```

2. **Manually: put the files in place**
- File: `.github/skills/product-launch-manager/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/ncklrs/startup-os-skills --path skills/product-launch-manager
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/product-launch-manager/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-launch-manager -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ncklrs/startup-os-skills/tree/HEAD/skills/product-launch-manager/SKILL.md

## When to use it
- 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
- 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

## Similar
- [launch](https://affpapa.org/en/nevibecode/skills/launch.md) — skill · 90600 installs
- [launch-strategy](https://affpapa.org/en/nevibecode/skills/openclaudia-launch-strategy.md) — skill · 458 installs
- [product-launch](https://affpapa.org/en/nevibecode/skills/product-launch.md) — skill · 1200 installs
- [product-launch-strategy](https://affpapa.org/en/nevibecode/skills/product-launch-strategy.md) — skill · 1300 installs
- [tracking-product-launch-buzz-on-twitter](https://affpapa.org/en/nevibecode/skills/tracking-product-launch-buzz-on-twitter.md) — skill · 886 installs
- [product-launch-war-room](https://affpapa.org/en/nevibecode/skills/product-launch-war-room.md) — skill · 159 installs

From the same set: [ncklrs/startup-os-skills](https://affpapa.org/en/nevibecode/by/ncklrs/startup-os-skills.md) — 51 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
