/project:launch#

Stage 7: Launch — Establishes Go-to-Market strategy, messaging, and analytics plan.

Triggers#

• When launch preparation is needed after Development completion
• When GTM strategy and marketing messages need to be established

Usage#

/project:launch
/project:launch --focus gtm
/project:launch --focus analytics

Options#

Skip Conditions#

This stage can be skipped in the following cases:

• Internal features (not exposed to users)
• Minor improvements (UI tweaks, bug fixes)
• Infrastructure changes

User confirmation is requested when skipping.

Prerequisites#

• Development stage completed
• Deployable code exists

Execution Flow#

Phase 1: GTM Strategy#

Source: cc-pm-gtm

1. GTM Motion (gtm-motion)

   • Product-Led vs Sales-Led decision
   • Channel strategy
   • Launch timeline

2. ICP Definition (icp-definition)

   • Ideal Customer Profile definition
   • Segment characteristics
   • Initial target segment

3. Messaging Framework (messaging-framework)

   • Positioning statement
   • Elevator pitch
   • Channel-specific message variants

Phase 2: Analytics Plan#

Source: cc-pm-analytics

4. A/B Test Design (ab-testing)

   • Test hypotheses
   • Variant design
   • Sample size calculation
   • Success metrics

5. Cohort Analysis (cohort-analysis)

   • Cohort definition
   • Tracking metrics
   • Analysis query design

Phase 3: Artifact Integration#

• Integrated document of GTM strategy + analytics plan
• Launch checklist generation

Artifacts#

docs/gtm-{slug}.md             # GTM strategy document
docs/analytics-plan-{slug}.md  # Analytics plan

After Completion#

• .pipeline/{slug}.yaml full pipeline set to completed
• Full project summary report output
• Artifact list cleanup