product-launch-manager

Name: product-launch-manager
Author: ncklrs

144installs3forks

How to install product-launch-manager?

ncklrs/startup-os-skills/product-launch-manager

$npx -y skills add ncklrs/startup-os-skills --skill product-launch-manager

Installs into the current project.

Summary

Expert product launch strategist for SaaS and technology companies. Use when planning product launches, coordinating cross-functional launch teams, managing beta programs, creating launch communication plans, planning launch day execution, setting up post-launch monitoring, runni

Files · 1

View on GitHub

SKILL.md

1	# Product Launch Manager
2
3	Strategic product launch expertise for technology companies — from launch planning and tiering to execution, monitoring, and retrospectives.
4
5	## Philosophy
6
7	Great launches aren't about the big bang. They're about orchestrated precision that maximizes impact while minimizing risk.
8
9	The best product launches:
10	1. Tier based on impact — Not every feature deserves a keynote
11	2. Coordinate ruthlessly — Cross-functional alignment is non-negotiable
12	3. Validate before announcing — Beta programs de-risk everything
13	4. Plan for failure — Rollback plans aren't pessimism, they're professionalism
14	5. Measure what matters — Success criteria before, not after, launch
15
16	## How This Skill Works
17
18	When invoked, apply the guidelines in `rules/` organized by:
19
20	- `planning-*` — Launch strategy, tiering, timelines, success criteria
21	- `coordination-*` — Cross-functional alignment, RACI, stakeholder management
22	- `beta-*` — Early access programs, beta cohorts, feedback loops
23	- `communication-*` — Internal enablement, external messaging, launch comms
24	- `execution-*` — Launch day operations, war rooms, monitoring
25	- `postlaunch-*` — Retrospectives, metrics analysis, iteration
26
27	## Core Frameworks
28
29	### Launch Tier Model
30
31	\| Tier \| Criteria \| Timeline \| Channels \| Example \|
32	\|------\|----------\|----------\|----------\|---------\|
33	\| Tier 1 \| New product, major platform shift \| 8-12 weeks \| Full press, event, keynote \| New product line \|
34	\| Tier 2 \| Major feature, significant expansion \| 4-8 weeks \| Blog, email, social, PR \| Enterprise feature \|
35	\| Tier 3 \| Feature enhancement, integration \| 2-4 weeks \| Blog, changelog, email \| New integration \|
36	\| Tier 4 \| Bug fix, minor improvement \| 1-2 weeks \| Changelog, in-app \| UI improvement \|
37
38	### Launch Readiness Model
39
40	```
41	┌─────────────────────────────────────────────────────────┐
42	│ LAUNCH READINESS │
43	├─────────────────────────────────────────────────────────┤
44	│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
45	│ │ Product │ │Marketing│ │ Sales │ │ Support │ │
46	│ │ Ready │ │ Ready │ │ Ready │ │ Ready │ │
47	│ └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘ │
48	│ │ │ │ │ │
49	│ └────────────┴─────┬──────┴────────────┘ │
50	│ │ │
51	│ ┌─────▼─────┐ │
52	│ │ GO/NO-GO │ │
53	│ │ DECISION │ │
54	│ └───────────┘ │
55	└─────────────────────────────────────────────────────────┘
56	```
57
58	### Launch RACI Matrix
59
60	\| Activity \| Product \| Marketing \| Sales \| Support \| Eng \| Exec \|
61	\|----------\|---------\|-----------\|-------\|---------\|-----\|------\|
62	\| Feature requirements \| A \| C \| C \| C \| R \| I \|
63	\| Launch tier decision \| R \| C \| C \| I \| C \| A \|
64	\| Launch date \| R \| C \| I \| I \| C \| A \|
65	\| External messaging \| C \| R \| C \| I \| I \| A \|
66	\| Internal enablement \| C \| R \| R \| R \| I \| I \|
67	\| Technical readiness \| C \| I \| I \| I \| R \| A \|
68	\| Support documentation \| C \| I \| I \| R \| C \| I \|
69	\| Go/no-go decision \| R \| R \| R \| R \| R \| A \|
70
71	R = Responsible, A = Accountable, C = Consulted, I = Informed
72
73	### Launch Timeline Template
74
75	```
76	Week -8: Launch brief, tier decision, stakeholder alignment
77	Week -6: Beta program begins, messaging draft
78	Week -4: Sales/support enablement starts, PR outreach
79	Week -2: Go/no-go checkpoint, final content review
80	Week -1: War room setup, monitoring configured, runbook complete
81	Day 0: LAUNCH
82	Week +1: Post-launch monitoring, quick fixes
83	Week +2: Launch retrospective, metrics review
84	```
85
86	### Success Criteria Framework
87
88	\| Category \| Metric Type \| Example \|
89	\|----------\|-------------\|---------\|
90	\| Adoption \| Usage metrics \| DAU, feature adoption rate, activation \|
91	\| Quality \| Stability metrics \| Error rate, P0 incidents, rollback rate \|
92	\| Business \| Revenue metrics \| Conversion, upsell, pipeline influence \|
93	\| Sentiment \| Feedback metrics \| NPS, support tickets, social sentiment \|
94
95	## Communication Templates
96
97	### Launch Brief Structure
98
99	```
100	1. Executive Summary
101	2. Launch Tier & Rationale
102	3. Target Audience
103	4. Key Messages (3 max)
104	5. Success Criteria
105	6. Timeline & Milestones
106	7. RACI & Stakeholders
107	8. Risks & Mitigations
108	9. Budget (if applicable)
109	10. Approval Sign-offs
110	```
111
112	### Go/No-Go Checklist
113
114	```
115	□ Product: Feature complete and tested
116	□ Product:

People who liked this also viewed

6 picks

Type

product-launch-manager

144installs3forks

View on GitHub

How to install product-launch-manager?

ncklrs/startup-os-skills/product-launch-manager

$npx -y skills add ncklrs/startup-os-skills --skill product-launch-manager

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Product Launch Manager
2
3	Strategic product launch expertise for technology companies — from launch planning and tiering to execution, monitoring, and retrospectives.
4
5	## Philosophy
6
7	Great launches aren't about the big bang. They're about orchestrated precision that maximizes impact while minimizing risk.
8
9	The best product launches:
10	1. Tier based on impact — Not every feature deserves a keynote
11	2. Coordinate ruthlessly — Cross-functional alignment is non-negotiable
12	3. Validate before announcing — Beta programs de-risk everything
13	4. Plan for failure — Rollback plans aren't pessimism, they're professionalism
14	5. Measure what matters — Success criteria before, not after, launch
15
16	## How This Skill Works
17
18	When invoked, apply the guidelines in `rules/` organized by:
19
20	- `planning-*` — Launch strategy, tiering, timelines, success criteria
21	- `coordination-*` — Cross-functional alignment, RACI, stakeholder management
22	- `beta-*` — Early access programs, beta cohorts, feedback loops
23	- `communication-*` — Internal enablement, external messaging, launch comms
24	- `execution-*` — Launch day operations, war rooms, monitoring
25	- `postlaunch-*` — Retrospectives, metrics analysis, iteration
26
27	## Core Frameworks
28
29	### Launch Tier Model
30
31	\| Tier \| Criteria \| Timeline \| Channels \| Example \|
32	\|------\|----------\|----------\|----------\|---------\|
33	\| Tier 1 \| New product, major platform shift \| 8-12 weeks \| Full press, event, keynote \| New product line \|
34	\| Tier 2 \| Major feature, significant expansion \| 4-8 weeks \| Blog, email, social, PR \| Enterprise feature \|
35	\| Tier 3 \| Feature enhancement, integration \| 2-4 weeks \| Blog, changelog, email \| New integration \|
36	\| Tier 4 \| Bug fix, minor improvement \| 1-2 weeks \| Changelog, in-app \| UI improvement \|
37
38	### Launch Readiness Model
39
40	```
41	┌─────────────────────────────────────────────────────────┐
42	│ LAUNCH READINESS │
43	├─────────────────────────────────────────────────────────┤
44	│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
45	│ │ Product │ │Marketing│ │ Sales │ │ Support │ │
46	│ │ Ready │ │ Ready │ │ Ready │ │ Ready │ │
47	│ └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘ │
48	│ │ │ │ │ │
49	│ └────────────┴─────┬──────┴────────────┘ │
50	│ │ │
51	│ ┌─────▼─────┐ │
52	│ │ GO/NO-GO │ │
53	│ │ DECISION │ │
54	│ └───────────┘ │
55	└─────────────────────────────────────────────────────────┘
56	```
57
58	### Launch RACI Matrix
59
60	\| Activity \| Product \| Marketing \| Sales \| Support \| Eng \| Exec \|
61	\|----------\|---------\|-----------\|-------\|---------\|-----\|------\|
62	\| Feature requirements \| A \| C \| C \| C \| R \| I \|
63	\| Launch tier decision \| R \| C \| C \| I \| C \| A \|
64	\| Launch date \| R \| C \| I \| I \| C \| A \|
65	\| External messaging \| C \| R \| C \| I \| I \| A \|
66	\| Internal enablement \| C \| R \| R \| R \| I \| I \|
67	\| Technical readiness \| C \| I \| I \| I \| R \| A \|
68	\| Support documentation \| C \| I \| I \| R \| C \| I \|
69	\| Go/no-go decision \| R \| R \| R \| R \| R \| A \|
70
71	R = Responsible, A = Accountable, C = Consulted, I = Informed
72
73	### Launch Timeline Template
74
75	```
76	Week -8: Launch brief, tier decision, stakeholder alignment
77	Week -6: Beta program begins, messaging draft
78	Week -4: Sales/support enablement starts, PR outreach
79	Week -2: Go/no-go checkpoint, final content review
80	Week -1: War room setup, monitoring configured, runbook complete
81	Day 0: LAUNCH
82	Week +1: Post-launch monitoring, quick fixes
83	Week +2: Launch retrospective, metrics review
84	```
85
86	### Success Criteria Framework
87
88	\| Category \| Metric Type \| Example \|
89	\|----------\|-------------\|---------\|
90	\| Adoption \| Usage metrics \| DAU, feature adoption rate, activation \|
91	\| Quality \| Stability metrics \| Error rate, P0 incidents, rollback rate \|
92	\| Business \| Revenue metrics \| Conversion, upsell, pipeline influence \|
93	\| Sentiment \| Feedback metrics \| NPS, support tickets, social sentiment \|
94
95	## Communication Templates
96
97	### Launch Brief Structure
98
99	```
100	1. Executive Summary
101	2. Launch Tier & Rationale
102	3. Target Audience
103	4. Key Messages (3 max)
104	5. Success Criteria
105	6. Timeline & Milestones
106	7. RACI & Stakeholders
107	8. Risks & Mitigations
108	9. Budget (if applicable)
109	10. Approval Sign-offs
110	```
111
112	### Go/No-Go Checklist
113
114	```
115	□ Product: Feature complete and tested
116	□ Product:

People who liked this also viewed

6 picks

Type