Kai Launch

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:

1. What's launching? (new product, feature, major update, rebrand)
2. Launch date — when does it go live?
3. Channels available — email list size, ad budget, social following, press contacts?
4. Offer/hook — any launch pricing, early access, beta invite?
5. Landing page — exists or needs to be created?

Phase 2: Launch Timeline

Generate workspace/launch/_timeline.md.

Standard Launch Phases

Asset Checklist

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

1. Landing page copy — defines the core messaging everyone else references
2. Press release — crystallizes the announcement narrative
3. Blog posts — expand on the story
4. Email sequences — use /kai-email-system workflow for the launch email set
5. Ad campaigns — use /kai-ad-campaign workflow for the ad set
6. Social posts — extract key lines from above assets
7. LinkedIn article — repurpose blog post for LinkedIn format

Per-Asset Production

Each asset follows the standard harness pipeline:

1. Load the right framework from knowledge/
2. Load the skill contract from harness/skill-contracts/
3. Load platform policy (for ads) from harness/references/
4. Write against the framework + persona
5. Run quality gates
6. 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

> **Kai root note:** `knowledge/`, `harness/`, and `scripts/` paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a `knowledge/` folder (the Kai plugin root, `~/.claude/kai`, or the kai-cmo-harness repo). `MARKETING.md`, `memory/`, and any output files live in the current project. If a referenced `scripts/` command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output.

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