when-releasing-new-product-orchestrate-product-launch
Use when launching a new product end-to-end from market research through post-launch monitoring. Orchestrates 15+ specialist agents across 5 phases in a 10-week coordinated workflow including research, development, marketing, sales preparation, launch execution, and ongoing optimization. Employs hierarchical coordination with parallel execution for efficiency and comprehensive coverage.
What this skill does
# Product Launch Orchestration Workflow
Complete end-to-end product launch workflow orchestrating 15+ specialist agents across research, development, marketing, launch execution, and post-launch monitoring. Designed for comprehensive product launches requiring coordination across technical, marketing, sales, and operations teams.
## Overview
This SOP orchestrates a complete 10-week product launch using multi-agent coordination with hierarchical topology. The workflow balances sequential dependencies with parallel execution to optimize both speed and quality. Each phase produces specific deliverables stored in memory for subsequent phases to consume, ensuring continuity and context preservation.
## Trigger Conditions
Use this workflow when:
- Launching a new product or major feature requiring comprehensive go-to-market
- Coordinating across multiple teams (engineering, marketing, sales, support)
- Need systematic approach covering all launch aspects from research to post-launch
- Timeline spans multiple weeks with clear phases and deliverables
- Require coordination between development, marketing campaigns, and sales enablement
- Post-launch monitoring and optimization are critical to success
## Orchestrated Agents (15 Total)
### Research & Planning Agents
- **`market-researcher`** - Market analysis, competitive research, customer insights, trend identification
- **`business-analyst`** - SWOT analysis, business model validation, revenue projections, risk assessment
- **`product-manager`** - Product strategy, feature prioritization, positioning, go-to-market planning
### Development & Engineering Agents
- **`backend-developer`** - REST/GraphQL API development, server-side logic, business layer implementation
- **`frontend-developer`** - Web UI development, React/Vue components, state management, client integration
- **`mobile-developer`** - iOS/Android applications, React Native, cross-platform, offline sync
- **`database-architect`** - Schema design, query optimization, indexing strategy, data modeling
- **`security-specialist`** - Security audits, vulnerability scanning, compliance validation, penetration testing
- **`qa-engineer`** - Test suite creation, integration testing, E2E testing, performance validation
### Marketing & Sales Agents
- **`marketing-specialist`** - Campaign creation, audience segmentation, multi-channel strategy, KPI tracking
- **`sales-specialist`** - Sales enablement, pipeline setup, lead qualification, revenue forecasting
- **`content-creator`** - Blog posts, social media content, email sequences, video scripts, landing pages
- **`seo-specialist`** - Keyword research, on-page SEO, link building, search optimization
### Launch & Operations Agents
- **`devops-engineer`** - CI/CD pipelines, Docker/K8s deployment, infrastructure setup, monitoring configuration
- **`production-validator`** - Production readiness assessment, go/no-go decision, deployment validation
- **`performance-monitor`** - Metrics collection, alert configuration, anomaly detection, dashboard setup
- **`customer-support-specialist`** - Support infrastructure, knowledge base, ticket workflows, team training
## Workflow Phases
### Phase 1: Research & Planning (Week 1-2, Sequential → Parallel)
**Duration**: 2 weeks
**Execution Mode**: Sequential analysis then parallel strategy
**Agents**: `market-researcher`, `business-analyst`, `product-manager`
**Process**:
1. **Conduct Comprehensive Market Analysis** (Day 1-3)
```bash
npx claude-flow hooks pre-task --description "Product launch: ${PRODUCT_NAME}"
npx claude-flow swarm init --topology hierarchical --max-agents 15
npx claude-flow agent spawn --type researcher
```
Spawn `market-researcher` agent to:
- Analyze target market size, demographics, and segmentation
- Research competitors (features, pricing, positioning, market share)
- Identify market trends, opportunities, and threats
- Document customer pain points and unmet needs
- Validate product-market fit hypotheses
**Memory Storage**:
```bash
npx claude-flow memory store --key "product-launch/${LAUNCH_ID}/phase-1/market-researcher/analysis" \
--value "${MARKET_ANALYSIS_JSON}"
```
2. **Perform Business Analysis** (Day 4-6)
Retrieve market analysis and spawn `business-analyst` agent:
```bash
npx claude-flow memory retrieve --key "product-launch/${LAUNCH_ID}/phase-1/market-researcher/analysis"
npx claude-flow agent spawn --type analyst
```
Conduct:
- SWOT analysis (Strengths, Weaknesses, Opportunities, Threats)
- Business model validation and monetization strategy
- Revenue projections and financial modeling (3-year forecast)
- Risk assessment and mitigation strategies
- Competitive differentiation analysis
**Memory Storage**:
```bash
npx claude-flow memory store --key "product-launch/${LAUNCH_ID}/phase-1/business-analyst/strategy"
```
3. **Define Product Strategy** (Day 7-10)
Retrieve market and business analysis, spawn `product-manager` agent:
```bash
npx claude-flow memory retrieve --pattern "product-launch/${LAUNCH_ID}/phase-1/*/analysis"
npx claude-flow agent spawn --type planner
```
Define:
- Product positioning statement and value proposition
- Feature prioritization (MVP vs future roadmap)
- Pricing strategy (tiers, packaging, discounts)
- Go-to-market strategy and launch timeline
- Success metrics and KPIs
**Memory Storage**:
```bash
npx claude-flow memory store --key "product-launch/${LAUNCH_ID}/phase-1/product-manager/plan"
npx claude-flow hooks post-task --task-id "phase-1-planning"
```
**Outputs**:
- Market analysis report with competitive landscape
- SWOT analysis and business validation
- Product strategy document with positioning and pricing
- Launch timeline with milestones
**Success Criteria**:
- [ ] Market opportunity clearly quantified (TAM, SAM, SOM)
- [ ] Competitive differentiation documented
- [ ] Business model validated with financial projections
- [ ] Product strategy approved by stakeholders
- [ ] Phase 1 deliverables stored in memory
---
### Phase 2: Product Development (Week 3-8, Parallel Execution)
**Duration**: 6 weeks
**Execution Mode**: Parallel with mesh coordination
**Agents**: `backend-developer`, `frontend-developer`, `mobile-developer`, `database-architect`, `security-specialist`, `qa-engineer`
**Process**:
1. **Initialize Development Swarm** (Day 1)
```bash
npx claude-flow swarm init --topology mesh --max-agents 6 --strategy adaptive
npx claude-flow memory retrieve --key "product-launch/${LAUNCH_ID}/phase-1/product-manager/plan"
```
2. **Parallel Development Execution** (Week 3-6)
Spawn all development agents concurrently:
```bash
# Backend development
npx claude-flow agent spawn --type backend-dev --capabilities "api,authentication,database"
# Frontend development
npx claude-flow agent spawn --type coder --capabilities "react,ui,state-management"
# Mobile development
npx claude-flow agent spawn --type mobile-dev --capabilities "react-native,ios,android"
# Database architecture
npx claude-flow agent spawn --type code-analyzer --capabilities "database,schema,optimization"
# Security implementation
npx claude-flow agent spawn --type reviewer --capabilities "security,audit,compliance"
# QA and testing
npx claude-flow agent spawn --type tester --capabilities "testing,automation,coverage"
```
**Backend Developer** builds:
- REST/GraphQL API with comprehensive endpoints
- Authentication system (OAuth 2.0, JWT)
- Business logic layer with validation
- Payment gateway integration
- Database integration and ORM setup
**Memory Pattern**: `product-launch/${LAUNCH_ID}/phase-2/backend-developer/{api-spec,schema,implementation}`
**Frontend Developer** builds:
- React/Vue web application with responsive design
- Component library following design system
- State managemRelated in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.