trainingsites/campus-ai-os/launch-planner

Launch Planner

Plan and coordinate a complete product or service launch — timeline, email sequence, social content, community announcement, and pre-launch checklist.

Setup Required

Kernel preamble §1 applies: references/kernel-preamble.md.

Before You Start

1. Read the resolved offers context — what's being launched and current offer stack
2. Read the resolved icp context — who you're launching to
3. Read the resolved brand context and the resolved voice context — voice and messaging
4. Read the resolved connections context (resolve per CONTEXT_CANON (.campus-os/context-files.md, else the plugin's templates/context-files.md): founding name → canon → alias, each also matched case-insensitively before the next; never hard-code a filename) — what platforms are available
5. Check the notes of the department whose roster holds email-sequence (kernel preamble §2) for any active campaigns

Inputs

The user provides:

• What's being launched — course, coaching program, service, product, event, webinar
• Launch date — when it goes live
• Price — or pricing structure
• Audience — who it's for (specific segment or full list)
• Constraints (optional) — budget, time, platform limitations

Steps

Step 1: Launch Strategy

Determine launch type:

Step 2: Build the Timeline

## Launch: [Offer Name]
**Launch date:** [Date]
**Type:** [Quick / Standard / Event]
 
### Pre-Launch (Week -2 to -1)
-[ ] Finalize offer details and pricing
-[ ] Write sales page copy (→ offer-builder skill)
-[ ] Create email sequence (→ email-sequence skill)
-[ ] Plan social content (→ social-planner skill)
-[ ] Prepare community announcement
-[ ] Set up checkout/payment page
 
### Launch Week
-**Day -1:** Teaser email + social post
-**Day 0:** Launch email + social blitz + community post
-**Day 1-3:** Value emails (address objections, share proof)
-**Day 5-7:** Last chance / cart close (if applicable)
 
### Post-Launch
-[ ] Thank buyers + deliver onboarding
-[ ] Review results: opens, clicks, conversions
-[ ] Debrief: what worked, what to change next time

Step 3: Create Launch Assets

Generate or delegate:

1. Email sequence — hand off to email-sequence skill (launch type, 3-5 emails)
2. Social content plan — 5-7 posts across the launch window
3. Community announcement — one post for the owner's community
4. Sales page outline — if needed, hand off to offer-builder skill

Step 4: Coordination Brief

Write a brief for each department involved:

• Content work → social posts and content assets (employees: content-repurposer, social-planner)
• Onboarding the people you serve → student/client onboarding prep (employees: student-comms, client-comms)
• Emails and launch execution (employees: email-sequence, launch-planner)

Name each department by the registry label of the roster that holds the employee (kernel preamble §2); never by a typed department name.

Drop briefs in the appropriate active-work/{department}/ folders.

Output

Save to outputs/YYYY-MM/plans/[launch-slug]/:

• launch-plan.md — Full timeline and checklist
• launch-emails/ — Email sequence (or reference to email-sequence output)
• launch-social.md — Social content plan
• community-announcement.md — Community post

Rules

• Every launch must have a clear deadline — open-ended launches don't convert
• Lead with transformation, not features
• Build urgency gradually — never start at max pressure
• Include a post-launch debrief step — launches that aren't reviewed don't improve