launch-planning

Name: launch-planning
Author: Productfculty-aipm

70stars33forks

How to install launch-planning?

productfculty-aipm/pm-copilot-by-product-faculty/launch-planning

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill launch-planning

Installs into the current project.

Summary

Use this skill when the user asks to "plan a launch", "create a launch plan", "how do I launch this feature", "launch checklist", "go-to-market plan for this feature", "launch timeline", "prepare for launch", or needs a structured plan for taking a feature or product from "ready

Files · 1

View on GitHub

SKILL.md

1	# Launch Planning
2
3	You are creating a launch plan — a structured timeline and checklist that ensures a feature or product is shipped, communicated, and measured effectively. Launches fail most often not because of product quality, but because of poor coordination, missing communications, or unmeasured impact.
4
5	Framework: April Dunford (positioning-first launch), Lenny Rachitsky (GTM frameworks), Teresa Torres (outcome measurement).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for product context, stakeholders, and stack (issue tracker, comms tools). Read `context/product/roadmap.md` for launch timeline and OKR context.
10
11	## Step 2 — Launch Scope Classification
12
13	Not all launches are created equal. Classify the launch to right-size the plan:
14
15	Tier 1 — Full launch (maximum coordination):
16	Major feature or product release. Affects most users. Requires: press/blog, email, in-app, coordinated sales/CS briefing, social media.
17	Examples: New product, major redesign, pricing change, new tier launch.
18
19	Tier 2 — Feature launch (moderate coordination):
20	Significant new capability. Affects a meaningful segment. Requires: in-app announcement, email to affected segment, CS briefing.
21	Examples: New integration, major workflow improvement, key requested feature.
22
23	Tier 3 — Incremental update (light coordination):
24	Quality improvements, minor features, bug fixes. Requires: changelog entry, brief CS note if it affects common workflows.
25	Examples: Performance improvements, small UX fixes, minor capability additions.
26
27	Ask the user which tier applies, or help them classify it.
28
29	## Step 3 — Pre-Launch Checklist
30
31	For Tier 1 or 2 launches, verify before launch day:
32
33	Product readiness:
34	- [ ] Feature is complete and tested in staging
35	- [ ] All acceptance criteria from the PRD are met
36	- [ ] Edge cases and failure modes are handled
37	- [ ] Analytics instrumentation is in place (can you measure success?)
38	- [ ] Feature flag configured (if applicable — allows instant rollback)
39
40	Content readiness:
41	- [ ] Launch announcement written (for each channel)
42	- [ ] Help documentation updated
43	- [ ] Support team briefed on what's changing and common questions
44	- [ ] Customer success team briefed (for any enterprise customers who need heads-up)
45
46	Coordination readiness:
47	- [ ] All stakeholders know the launch date
48	- [ ] Sales team briefed (if applicable)
49	- [ ] Leadership is aware
50	- [ ] External partners notified (if this affects an integration)
51
52	Measurement readiness:
53	- [ ] Success metrics are defined and instrumented
54	- [ ] Baseline measurements taken before launch
55	- [ ] First review date scheduled (T+7 days)
56
57	## Step 4 — Launch Timeline
58
59	Build a launch timeline working backward from the launch date:
60
61	\| T- \| Action \| Owner \|
62	\|---\|---\|---\|
63	\| T-14 \| Feature complete in staging; acceptance criteria review \| Engineering \|
64	\| T-10 \| Write all launch communications; send to stakeholders for review \| PM \|
65	\| T-7 \| Finalize help docs; brief support team \| PM + Support \|
66	\| T-5 \| Brief CS/Sales; confirm partner notifications sent \| PM + CS \|
67	\| T-3 \| Final testing in staging; confirm feature flag is ready \| Engineering \|
68	\| T-1 \| All communications pre-scheduled; team on standby \| PM \|
69	\| T-0 \| Deploy to production; activate feature flag; publish communications \| Engineering + PM \|
70	\| T+1 \| Monitor metrics; address early support volume \| PM \|
71	\| T+7 \| First metrics review; quick wins documented \| PM \|
72	\| T+14 \| Full impact assessment; lessons captured \| PM \|
73
74	## Step 5 — Rollback Plan
75
76	Define the rollback plan before launch day:
77
78	- Trigger: At what metric threshold would we roll back? (e.g., error rate > 5%, core metric drops > 10%)
79	- How to roll back: Feature flag? Code revert? Who executes it?
80	- Who decides to roll back? One named decision-maker — not a committee
81	- Communication plan: What do we tell users if we roll back?
82
83	## Step 6 — Post-Launch Review
84
85	Schedule:
86	- T+7 day review: Is the feature being used? Are there unexpected issues? Is the metric moving?
87	- T+30 day review: Full impact assessment against success metrics from the PRD. Document lessons learned.
88	- Memory update: Offer to save launch lessons to `memory/user-profile.md`
89
90	## Step 7 — Output
91
92	Produce:
93	- Launch tier classification with rationale
94	- Pre-launch checklist (completed with owners and deadlines)
95	- Launch timeline table
96	- Rollback plan
97	- Post-launch review schedule
98	- Draft launch announcement (or reference the launch-announcement skill)

People who liked this also viewed

6 picks

Type

launch-planning

70stars33forks

View on GitHub

How to install launch-planning?

productfculty-aipm/pm-copilot-by-product-faculty/launch-planning

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill launch-planning

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Launch Planning
2
3	You are creating a launch plan — a structured timeline and checklist that ensures a feature or product is shipped, communicated, and measured effectively. Launches fail most often not because of product quality, but because of poor coordination, missing communications, or unmeasured impact.
4
5	Framework: April Dunford (positioning-first launch), Lenny Rachitsky (GTM frameworks), Teresa Torres (outcome measurement).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for product context, stakeholders, and stack (issue tracker, comms tools). Read `context/product/roadmap.md` for launch timeline and OKR context.
10
11	## Step 2 — Launch Scope Classification
12
13	Not all launches are created equal. Classify the launch to right-size the plan:
14
15	Tier 1 — Full launch (maximum coordination):
16	Major feature or product release. Affects most users. Requires: press/blog, email, in-app, coordinated sales/CS briefing, social media.
17	Examples: New product, major redesign, pricing change, new tier launch.
18
19	Tier 2 — Feature launch (moderate coordination):
20	Significant new capability. Affects a meaningful segment. Requires: in-app announcement, email to affected segment, CS briefing.
21	Examples: New integration, major workflow improvement, key requested feature.
22
23	Tier 3 — Incremental update (light coordination):
24	Quality improvements, minor features, bug fixes. Requires: changelog entry, brief CS note if it affects common workflows.
25	Examples: Performance improvements, small UX fixes, minor capability additions.
26
27	Ask the user which tier applies, or help them classify it.
28
29	## Step 3 — Pre-Launch Checklist
30
31	For Tier 1 or 2 launches, verify before launch day:
32
33	Product readiness:
34	- [ ] Feature is complete and tested in staging
35	- [ ] All acceptance criteria from the PRD are met
36	- [ ] Edge cases and failure modes are handled
37	- [ ] Analytics instrumentation is in place (can you measure success?)
38	- [ ] Feature flag configured (if applicable — allows instant rollback)
39
40	Content readiness:
41	- [ ] Launch announcement written (for each channel)
42	- [ ] Help documentation updated
43	- [ ] Support team briefed on what's changing and common questions
44	- [ ] Customer success team briefed (for any enterprise customers who need heads-up)
45
46	Coordination readiness:
47	- [ ] All stakeholders know the launch date
48	- [ ] Sales team briefed (if applicable)
49	- [ ] Leadership is aware
50	- [ ] External partners notified (if this affects an integration)
51
52	Measurement readiness:
53	- [ ] Success metrics are defined and instrumented
54	- [ ] Baseline measurements taken before launch
55	- [ ] First review date scheduled (T+7 days)
56
57	## Step 4 — Launch Timeline
58
59	Build a launch timeline working backward from the launch date:
60
61	\| T- \| Action \| Owner \|
62	\|---\|---\|---\|
63	\| T-14 \| Feature complete in staging; acceptance criteria review \| Engineering \|
64	\| T-10 \| Write all launch communications; send to stakeholders for review \| PM \|
65	\| T-7 \| Finalize help docs; brief support team \| PM + Support \|
66	\| T-5 \| Brief CS/Sales; confirm partner notifications sent \| PM + CS \|
67	\| T-3 \| Final testing in staging; confirm feature flag is ready \| Engineering \|
68	\| T-1 \| All communications pre-scheduled; team on standby \| PM \|
69	\| T-0 \| Deploy to production; activate feature flag; publish communications \| Engineering + PM \|
70	\| T+1 \| Monitor metrics; address early support volume \| PM \|
71	\| T+7 \| First metrics review; quick wins documented \| PM \|
72	\| T+14 \| Full impact assessment; lessons captured \| PM \|
73
74	## Step 5 — Rollback Plan
75
76	Define the rollback plan before launch day:
77
78	- Trigger: At what metric threshold would we roll back? (e.g., error rate > 5%, core metric drops > 10%)
79	- How to roll back: Feature flag? Code revert? Who executes it?
80	- Who decides to roll back? One named decision-maker — not a committee
81	- Communication plan: What do we tell users if we roll back?
82
83	## Step 6 — Post-Launch Review
84
85	Schedule:
86	- T+7 day review: Is the feature being used? Are there unexpected issues? Is the metric moving?
87	- T+30 day review: Full impact assessment against success metrics from the PRD. Document lessons learned.
88	- Memory update: Offer to save launch lessons to `memory/user-profile.md`
89
90	## Step 7 — Output
91
92	Produce:
93	- Launch tier classification with rationale
94	- Pre-launch checklist (completed with owners and deadlines)
95	- Launch timeline table
96	- Rollback plan
97	- Post-launch review schedule
98	- Draft launch announcement (or reference the launch-announcement skill)

People who liked this also viewed

6 picks

Type