Orchestrate a complete product launch — coordinates emails, ads, content, PR, and social into a unified campaign with a timeline.
Phase 0: Load Product Context
Check if MARKETING.md exists in the project root (same directory as CLAUDE.md, README.md, package.json).
If it exists: Read it — skip product discovery questions. It has the product name, ICP, value prop, monetization, brand voice, current channels, and competitive landscape.
If it does NOT exist: Auto-explore the codebase to create it in the project root (next to CLAUDE.md). Do NOT ask the user what the product is. Read CLAUDE.md, README.md, PROJECT.md, package.json, landing pages, and any project files. Search for email/ad/analytics config. Then create MARKETING.md using the template from /kai-email-system. Present draft to user for confirmation.
Phase 1: Launch Discovery
Read from MARKETING.md. Only ask about things not covered there:
- What's launching? (new product, feature, major update, rebrand)
- Launch date — when does it go live?
- Channels available — email list size, ad budget, social following, press contacts?
- Offer/hook — any launch pricing, early access, beta invite?
- Landing page — exists or needs to be created?
Phase 2: Launch Timeline
Generate workspace/launch/_timeline.md.
Standard Launch Phases
| Phase |
Timing |
Activities |
| Pre-launch |
T-14 to T-7 |
Teaser emails, waitlist, social hints, internal prep |
| Warm-up |
T-7 to T-1 |
Blog post(s), detailed previews, influencer/press outreach |
| Launch Day |
T-0 |
Announcement email, ad campaigns go live, press release, social blitz |
| Post-launch |
T+1 to T+14 |
Nurture sequence, retargeting ads, case study collection, performance review |
| Sustain |
T+14 to T+30 |
Content marketing, SEO articles, ongoing ads optimization |
Asset Checklist
| Asset |
Channel |
Phase |
Status |
| Landing page copy |
Web |
Pre-launch |
Needed |
| Teaser email (1-2) |
Loops |
Pre-launch |
Needed |
| Announcement email |
Loops |
Launch day |
Needed |
| Follow-up email sequence (3-5) |
Loops |
Post-launch |
Needed |
| Meta ads — TOF (3 variants) |
Meta |
Launch day |
Needed |
| Meta ads — retarget (3 variants) |
Meta |
Post-launch |
Needed |
| Google ads — brand (RSA) |
Google |
Launch day |
Needed |
| Google ads — non-brand (RSA) |
Google |
Launch day |
Needed |
| Blog post — announcement |
Blog |
Warm-up |
Needed |
| Blog post — deep dive |
Blog |
Post-launch |
Needed |
| LinkedIn article |
LinkedIn |
Launch day |
Needed |
| Press release |
PR |
Launch day |
Needed |
| Social posts (5-10) |
Social |
All phases |
Needed |
Adapt to the actual launch. Remove assets for channels the user doesn't have.
Approval Gate
Present the timeline and asset checklist. Confirm before producing anything.
Phase 3: Batch Production
Produce assets in dependency order:
Order of Operations
- Landing page copy — defines the core messaging everyone else references
- Press release — crystallizes the announcement narrative
- Blog posts — expand on the story
- Email sequences — use
/kai-email-system workflow for the launch email set
- Ad campaigns — use
/kai-ad-campaign workflow for the ad set
- Social posts — extract key lines from above assets
- LinkedIn article — repurpose blog post for LinkedIn format
Per-Asset Production
Each asset follows the standard harness pipeline:
- Load the right framework from
E:\Dev2\kai-cmo-harness-work\knowledge/
- Load the skill contract from
harness/skill-contracts/
- Load platform policy (for ads) from
harness/references/
- Write against the framework + persona
- Run quality gates
- Max 2 retries per asset
Messaging Consistency
All assets must use the same:
- Core value proposition (defined in landing page copy)
- Key stats/proof points (consistent across all channels)
- CTA (same destination — landing page or signup)
- Persona hooks (same pain points, same language)
Extract these from the landing page copy and use as a reference for all subsequent assets.
Batch Output
workspace/launch/
├── _timeline.md
├── _messaging-guide.md # Core VP, stats, CTA, extracted from landing page
├── landing-page/
│ └── copy.md
├── emails/
│ ├── teaser-1.md
│ ├── teaser-2.md
│ ├── announcement.md
│ ├── follow-up-1.md
│ └── follow-up-2.md
├── ads/
│ ├── meta/
│ └── google/
├── blog/
│ ├── announcement.md
│ └── deep-dive.md
├── pr/
│ └── press-release.md
├── social/
│ ├── launch-day-posts.md
│ └── sustain-posts.md
├── linkedin/
│ └── article.md
└── _quality-report.md
Phase 4: Quality Report
# Launch Campaign Quality Report
## Summary
- Total assets: [N]
- Passed all gates: [N]
- Channels covered: [list]
- Messaging consistency: [PASS/FAIL — same VP across all assets?]
## Per-Asset Results
| Asset | Channel | Four U's | Banned | Policy | Status |
|-------|---------|----------|--------|--------|--------|
## Launch Readiness
- [ ] Landing page copy approved
- [ ] Email sequences loaded in Loops
- [ ] Ad campaigns ready to activate
- [ ] Press release ready to distribute
- [ ] Blog posts scheduled
- [ ] Social posts queued
Phase 5: Post-Launch Monitoring Plan
Generate workspace/launch/_monitoring.md:
- Day 1, 3, 7, 14 check-in schedule
- Metrics to watch per channel (email open rates, ad CTR, landing page conversion)
- When to adjust (kill underperforming ads, boost winners)
- Content to produce based on early results (FAQ post, case study, feature tutorial)
1---2name: kai-launch3description: Plan and produce a complete product launch marketing package — landing page copy, email sequences, ad campaigns, press release, social posts, and launch timeline. Orchestrates all other kai skills into a coordinated launch. Use when "product launch", "launch campaign", "go-to-market", "GTM plan", "launch marketing", "we're launching", "prepare launch materials", or any request to coordinate marketing for a new product, feature, or major update.4---5
6Orchestrate a complete product launch — coordinates emails, ads, content, PR, and social into a unified campaign with a timeline.
7
8## Phase 0: Load Product Context
9
10Check if `MARKETING.md` exists in the **project root** (same directory as CLAUDE.md, README.md, package.json).
11
12**If it exists:** Read it — skip product discovery questions. It has the product name, ICP, value prop, monetization, brand voice, current channels, and competitive landscape.
13
14**If it does NOT exist:** Auto-explore the codebase to create it in the **project root** (next to CLAUDE.md). Do NOT ask the user what the product is. Read CLAUDE.md, README.md, PROJECT.md, package.json, landing pages, and any project files. Search for email/ad/analytics config. Then create `MARKETING.md` using the template from `/kai-email-system`. Present draft to user for confirmation.
15
16---
17
18## Phase 1: Launch Discovery
19
20Read from `MARKETING.md`. Only ask about things not covered there:
21
221. **What's launching?** (new product, feature, major update, rebrand)
232. **Launch date** — when does it go live?
243. **Channels available** — email list size, ad budget, social following, press contacts?
254. **Offer/hook** — any launch pricing, early access, beta invite?
265. **Landing page** — exists or needs to be created?
27
28## Phase 2: Launch Timeline
29
30Generate `workspace/launch/_timeline.md`.
31
32### Standard Launch Phases
33
34| Phase | Timing | Activities |
35|-------|--------|------------|
36| **Pre-launch** | T-14 to T-7 | Teaser emails, waitlist, social hints, internal prep |
37| **Warm-up** | T-7 to T-1 | Blog post(s), detailed previews, influencer/press outreach |
38| **Launch Day** | T-0 | Announcement email, ad campaigns go live, press release, social blitz |
39| **Post-launch** | T+1 to T+14 | Nurture sequence, retargeting ads, case study collection, performance review |
40| **Sustain** | T+14 to T+30 | Content marketing, SEO articles, ongoing ads optimization |
41
42### Asset Checklist
43
44| Asset | Channel | Phase | Status |
45|-------|---------|-------|--------|
46| Landing page copy | Web | Pre-launch | Needed |
47| Teaser email (1-2) | Loops | Pre-launch | Needed |
48| Announcement email | Loops | Launch day | Needed |
49| Follow-up email sequence (3-5) | Loops | Post-launch | Needed |
50| Meta ads — TOF (3 variants) | Meta | Launch day | Needed |
51| Meta ads — retarget (3 variants) | Meta | Post-launch | Needed |
52| Google ads — brand (RSA) | Google | Launch day | Needed |
53| Google ads — non-brand (RSA) | Google | Launch day | Needed |
54| Blog post — announcement | Blog | Warm-up | Needed |
55| Blog post — deep dive | Blog | Post-launch | Needed |
56| LinkedIn article | LinkedIn | Launch day | Needed |
57| Press release | PR | Launch day | Needed |
58| Social posts (5-10) | Social | All phases | Needed |
59
60Adapt to the actual launch. Remove assets for channels the user doesn't have.
61
62### Approval Gate
63
64Present the timeline and asset checklist. Confirm before producing anything.
65
66## Phase 3: Batch Production
67
68Produce assets in dependency order:
69
70### Order of Operations
71
721. **Landing page copy** — defines the core messaging everyone else references
732. **Press release** — crystallizes the announcement narrative
743. **Blog posts** — expand on the story
754. **Email sequences** — use `/kai-email-system` workflow for the launch email set
765. **Ad campaigns** — use `/kai-ad-campaign` workflow for the ad set
776. **Social posts** — extract key lines from above assets
787. **LinkedIn article** — repurpose blog post for LinkedIn format
79
80### Per-Asset Production
81
82Each asset follows the standard harness pipeline:
83
841. Load the right framework from `E:\Dev2\kai-cmo-harness-work\knowledge/`
852. Load the skill contract from `harness/skill-contracts/`
863. Load platform policy (for ads) from `harness/references/`
874. Write against the framework + persona
885. Run quality gates
896. Max 2 retries per asset
90
91### Messaging Consistency
92
93All assets must use the same:
94- **Core value proposition** (defined in landing page copy)
95- **Key stats/proof points** (consistent across all channels)
96- **CTA** (same destination — landing page or signup)
97- **Persona hooks** (same pain points, same language)
98
99Extract these from the landing page copy and use as a reference for all subsequent assets.
100
101### Batch Output
102
103```
104workspace/launch/
105├── _timeline.md
106├── _messaging-guide.md # Core VP, stats, CTA, extracted from landing page
107├── landing-page/
108│ └── copy.md
109├── emails/
110│ ├── teaser-1.md
111│ ├── teaser-2.md
112│ ├── announcement.md
113│ ├── follow-up-1.md
114│ └── follow-up-2.md
115├── ads/
116│ ├── meta/
117│ └── google/
118├── blog/
119│ ├── announcement.md
120│ └── deep-dive.md
121├── pr/
122│ └── press-release.md
123├── social/
124│ ├── launch-day-posts.md
125│ └── sustain-posts.md
126├── linkedin/
127│ └── article.md
128└── _quality-report.md
129```
130
131## Phase 4: Quality Report
132
133```markdown
134# Launch Campaign Quality Report
135
136## Summary
137- Total assets: [N]
138- Passed all gates: [N]
139- Channels covered: [list]
140- Messaging consistency: [PASS/FAIL — same VP across all assets?]
141
142## Per-Asset Results
143| Asset | Channel | Four U's | Banned | Policy | Status |
144|-------|---------|----------|--------|--------|--------|
145
146## Launch Readiness
147- [ ] Landing page copy approved
148- [ ] Email sequences loaded in Loops
149- [ ] Ad campaigns ready to activate
150- [ ] Press release ready to distribute
151- [ ] Blog posts scheduled
152- [ ] Social posts queued
153```
154
155## Phase 5: Post-Launch Monitoring Plan
156
157Generate `workspace/launch/_monitoring.md`:
158- Day 1, 3, 7, 14 check-in schedule
159- Metrics to watch per channel (email open rates, ad CTR, landing page conversion)
160- When to adjust (kill underperforming ads, boost winners)
161- Content to produce based on early results (FAQ post, case study, feature tutorial)
majiayu000