How do I install the Product Launch skill?

Run npx skillmds@latest add ashutoshsrivastava17/product-launch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Product Launch safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Product Launch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Product Launch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Product Launch?

ashutoshsrivastava17 (@ashutoshsrivastava17) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Product Launch by ashutoshsrivastava17

Name: Product Launch
Author: ashutoshsrivastava17

Product Launch

Plan product launches — launch tiers, go/no-go criteria, cross-functional checklist, communication plan, enablement, and post-launch review. TRIGGER when: user says /product-launch or asks about launching a product or feature.

File contents

Product Launch Plan

Process

Step 1: Define Launch Tier

Tier	Scope	Activities
T1 (Major)	New product, major feature	Full GTM, PR, event, enablement
T2 (Standard)	Significant feature	Blog, email, in-app, enablement
T3 (Minor)	Improvement, fix	Changelog, in-app notification

Step 2: Set Go/No-Go Criteria

Category	Criteria	Status
Product	Feature complete, QA passed	☐
Performance	Load tested, SLAs met	☐
Documentation	Help docs, API docs updated	☐
Enablement	Sales/support trained	☐
Marketing	Assets ready, campaigns scheduled	☐
Legal	Terms updated, compliance reviewed	☐

Step 3: Cross-Functional Checklist

Team	Deliverables	Owner	Due
Engineering	Feature deployed, monitoring live	[name]	[date]
Design	Assets, screenshots, demo video	[name]	[date]
Marketing	Blog, email, social, landing page	[name]	[date]
Sales	Pitch deck, battle card, FAQ	[name]	[date]
Support	KB articles, runbook, training	[name]	[date]
Legal	Terms, privacy, compliance	[name]	[date]

Step 4: Communication Plan

Audience	Channel	Timing	Message
Internal	All-hands, Slack	T-1 week	Preview and enablement
Customers	Email, in-app	Launch day	Announcement
Prospects	Blog, social, PR	Launch day	Value proposition
Partners	Email, portal	T-1 day	Enablement materials

Step 5: Launch Execution

Time	Action	Owner
T-7 days	Final go/no-go meeting	PM
T-1 day	Staged deployment	Engineering
Launch day	Flip feature flag, publish content	PM + Marketing
T+1 day	Monitor metrics, respond to feedback	All
T+7 days	First week review	PM

Step 6: Post-Launch Review

Metric	Target	Actual
Adoption	X% in first month	X%
Satisfaction	X/5 CSAT	X/5
Support tickets	< X related tickets	X
Revenue impact	$X pipeline influenced	$X

Output Format

## Launch Plan: [Product/Feature]
### Tier: [T1/T2/T3]
### Go/No-Go: [Criteria with status]
### Timeline: [Key dates]
### Metrics: [Success criteria]

Quality Checklist

Launch tier determines appropriate activities
Go/no-go criteria are specific and measurable
All teams have clear deliverables and deadlines
Communication covers all audiences
Post-launch review scheduled

Edge Cases

For beta-to-GA transitions, communicate changes since beta
For breaking changes, extend communication timeline
If launch timing is competitive, plan for confidentiality

---name: product-launchdescription: Plan product launches — launch tiers, go/no-go criteria, cross-functional checklist, communication plan, enablement, and post-launch review. TRIGGER when: user says /product-launch or asks about launching a product or feature.---# Product Launch Plan## Process### Step 1: Define Launch Tier| Tier | Scope | Activities ||------|-------|-----------|| T1 (Major) | New product, major feature | Full GTM, PR, event, enablement || T2 (Standard) | Significant feature | Blog, email, in-app, enablement || T3 (Minor) | Improvement, fix | Changelog, in-app notification |### Step 2: Set Go/No-Go Criteria| Category | Criteria | Status ||----------|---------|--------|| Product | Feature complete, QA passed | ☐ || Performance | Load tested, SLAs met | ☐ || Documentation | Help docs, API docs updated | ☐ || Enablement | Sales/support trained | ☐ || Marketing | Assets ready, campaigns scheduled | ☐ || Legal | Terms updated, compliance reviewed | ☐ |### Step 3: Cross-Functional Checklist| Team | Deliverables | Owner | Due ||------|-------------|-------|-----|| Engineering | Feature deployed, monitoring live | [name] | [date] || Design | Assets, screenshots, demo video | [name] | [date] || Marketing | Blog, email, social, landing page | [name] | [date] || Sales | Pitch deck, battle card, FAQ | [name] | [date] || Support | KB articles, runbook, training | [name] | [date] || Legal | Terms, privacy, compliance | [name] | [date] |### Step 4: Communication Plan| Audience | Channel | Timing | Message ||----------|---------|--------|---------|| Internal | All-hands, Slack | T-1 week | Preview and enablement || Customers | Email, in-app | Launch day | Announcement || Prospects | Blog, social, PR | Launch day | Value proposition || Partners | Email, portal | T-1 day | Enablement materials |### Step 5: Launch Execution| Time | Action | Owner ||------|--------|-------|| T-7 days | Final go/no-go meeting | PM || T-1 day | Staged deployment | Engineering || Launch day | Flip feature flag, publish content | PM + Marketing || T+1 day | Monitor metrics, respond to feedback | All || T+7 days | First week review | PM |### Step 6: Post-Launch Review| Metric | Target | Actual | Notes ||--------|--------|--------|-------|| Adoption | X% in first month | X% | || Satisfaction | X/5 CSAT | X/5 | || Support tickets | < X related tickets | X | || Revenue impact | $X pipeline influenced | $X | |## Output Format```markdown## Launch Plan: [Product/Feature]### Tier: [T1/T2/T3]### Go/No-Go: [Criteria with status]### Timeline: [Key dates]### Metrics: [Success criteria]```## Quality Checklist- [ ] Launch tier determines appropriate activities- [ ] Go/no-go criteria are specific and measurable- [ ] All teams have clear deliverables and deadlines- [ ] Communication covers all audiences- [ ] Post-launch review scheduled## Edge Cases- For beta-to-GA transitions, communicate changes since beta- For breaking changes, extend communication timeline- If launch timing is competitive, plan for confidentiality

Frequently asked questions