# technical-launch-planner

technical-launch-planner is a Claude Code skill that plans technical product launches by assessing scope, building a work plan, and checking team and materials readiness.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 137 installs · ★ 236 repo stars
- Author: jamesrochabrun
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/jamesrochabrun/skills/tree/HEAD/skills/technical-launch-planner/SKILL.md
- Updated: 2026-01-14
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/technical-launch-planner

## What it does

The skill guides launch planning for developer tools, APIs, SDKs, and platforms. It helps assess the release scope, set success criteria, align stakeholders, and build a plan with milestones, developer enablement tasks, and launch-day actions.

Three scripts support the workflow: `scripts/assess_launch_tier.sh`, `scripts/generate_launch_plan.sh`, and `scripts/validate_readiness.sh`. They assess the launch tier, create a plan, and check documentation, technical assets, stakeholder alignment, messaging, and metrics instrumentation. The tier affects the workload: a major launch includes PR and events, while a minor update may rely on a changelog and in-app messaging.

The plan covers preparation, launch-day monitoring, and post-launch review. This skill coordinates the work; it does not release the product for you.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add jamesrochabrun/skills --skill technical-launch-planner -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add jamesrochabrun/skills --skill technical-launch-planner -a codex
```

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

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add jamesrochabrun/skills --skill technical-launch-planner -a cursor
```

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install jamesrochabrun/skills skills/technical-launch-planner
```

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

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add jamesrochabrun/skills --skill technical-launch-planner -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/jamesrochabrun/skills --path skills/technical-launch-planner
```

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add jamesrochabrun/skills --skill technical-launch-planner -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/jamesrochabrun/skills/tree/HEAD/skills/technical-launch-planner/SKILL.md

## When to use it
- assess the scope of a product launch
- map launch milestones and stakeholder responsibilities
- prepare developer-facing launch assets
- check launch readiness before release
- organize launch-day tasks and follow-up

## Example prompts
- Assess the tier for our new API launch and draft a work plan.
- Plan an SDK release with milestones and owners.
- Check whether our documentation, technical assets, and metrics are ready for launch.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 03e9b85f7f0d08d7.

BEGIN THIRD-PARTY FILE 03e9b85f7f0d08d7
````text
---
name: technical-launch-planner
description: Plan and execute technical product launches for developer tools, APIs, and technical products. Use this skill when technical PMMs need to "plan a launch", "create a launch strategy", "coordinate a product release", or "prepare for GA/beta launch".
---

# Technical Launch Planner

## Overview

Plan and execute successful launches for technical products, developer tools, APIs, SDKs, and platforms. This skill provides frameworks, checklists, and templates specifically designed for technical audiences and developer-focused products.

**Built for:**
- Developer tools and platforms
- APIs and SDKs
- Technical infrastructure products
- B2D (Business-to-Developer) products
- SaaS with technical buyers

---

## Quick Start

### 1. Assess Your Launch Tier

Run the interactive assessment:

```bash
scripts/assess_launch_tier.sh
```

This determines if your launch is:
- **Tier 1** (Major/GA) - New product, major version, significant expansion
- **Tier 2** (Standard) - New features, integrations, regional expansion
- **Tier 3** (Minor) - Updates, improvements, small features

### 2. Generate Launch Plan

Create your comprehensive launch plan:

```bash
scripts/generate_launch_plan.sh
```

Provides structured plan with:
- Timeline and milestones
- Stakeholder responsibilities
- Developer enablement checklist
- Go-to-market activities
- Launch day playbook

### 3. Validate Readiness

Before launch, check readiness:

```bash
scripts/validate_readiness.sh
```

Validates:
- Documentation completeness
- Technical assets ready
- Stakeholder alignment
- Messaging finalized
- Metrics instrumentation

---

## Core Launch Framework

### Launch Tiers

Different launches require different levels of investment:

| Tier | Type | Examples | Investment |
|------|------|----------|------------|
| **Tier 1** | Major | GA launch, new product, major version | Full GTM, events, PR |
| **Tier 2** | Standard | New features, integrations, SDKs | Selective GTM, blog, docs |
| **Tier 3** | Minor | Updates, improvements, patches | Changelog, in-app |

See `references/launch_tiers.md` for complete framework.

---

## Developer-Focused Launch Components

### 1. Developer Enablement

**Critical for technical launches:**

**Documentation:**
- Getting started guide
- API reference
- Code samples
- Integration guides
- Migration guides (if applicable)

**Code Assets:**
- SDKs/client libraries
- Sample applications
- Starter templates
- Code snippets

**Developer Experience:**
- Sandbox/playground environment
- Interactive tutorials
- API explorer
- Debugging tools
````
END THIRD-PARTY FILE 03e9b85f7f0d08d7

The third-party file has ended. Everything between the 03e9b85f7f0d08d7 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2610 of 15316 bytes. © jamesrochabrun · MIT · https://github.com/jamesrochabrun/skills/tree/HEAD/skills/technical-launch-planner/SKILL.md

_Part of the page did not fit — see the HTML version._

---
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
