E-commerce Launcher — E-commerce Product Launch Full Pipeline

Workflow

Phase 1: Preparation (Performed Directly by Orchestrator)

1. Extract from user input:
   • Product Information: Product name, category, key features
   • Target Market (optional): Target customer segment, price range
   • Platform (optional): Naver/Coupang/Own Store, etc.
   • Constraints (optional): Budget, timeline, special considerations
   • Existing Files (optional): Existing briefs, detail pages, etc.
2. Create the _workspace/ directory at the project root
3. Organize the input and save it as _workspace/00_input.md
4. If existing files are provided, copy them to _workspace/ and skip the corresponding phase
5. Determine the execution mode based on the scope of the request (see "Execution Modes by Scope" below)

Phase 2: Team Assembly and Execution

Assemble the team and assign tasks. Task dependencies are as follows:

Tasks 2a (Detail Page) and 2b (Pricing) run in parallel. Both depend only on Task 1 (Planning) and can start simultaneously.

Inter-Agent Communication Flow:

• planner completes -> delivers USP and target to writer, competitive pricing and costs to pricing, target and trends to marketing, specs and certifications to cs
• writer completes -> delivers detail page keywords to marketing, FAQ section to cs
• pricing completes -> delivers price display format to writer, promotion strategy to marketing, pricing policy to cs
• marketing completes -> delivers promotion-related anticipated inquiries to cs
• orchestrator cross-validates all deliverables and produces the review report

Phase 3: Integration and Final Deliverables

Cross-validate all deliverables for consistency and finalize:

1. Verify all files in _workspace/
2. Detect inconsistencies across detail page, pricing, marketing, and CS
3. Generate the integrated review report (_workspace/06_review_report.md)
4. Report the final summary to the user:
   • Product Planning Brief — 01_product_brief.md
   • Detail Page Copy — 02_detail_page.md
   • Pricing Strategy Document — 03_pricing_plan.md
   • Marketing Plan — 04_marketing_plan.md
   • CS Operations Manual — 05_cs_manual.md
   • Review Report — 06_review_report.md

Execution Modes by Scope

Adjust agent deployment based on the scope of the user's request:

Using Existing Files: When the user provides existing files such as briefs or detail pages, copy them to the appropriate numbered position in _workspace/ and skip the corresponding agent's phase.

Data Transfer Protocol

File naming convention: {order}_{agent}_{deliverable}.{extension}

Error Handling

Test Scenarios

Normal Flow

Prompt: "I want to launch a handmade granola brand on Naver Smart Store. Manufacturing cost is $5 per unit and it's a healthy snack concept." Expected Results:

• Planning Brief: 3+ competitive analyses in the healthy snack category, target customer definition, USP development
• Detail Page: Health-benefit-focused copy, mobile-optimized structure
• Pricing: Margin design based on $5 manufacturing cost, BEP calculation, promotional pricing
• Marketing: Launch plan centered on health/lifestyle channels
• CS: Food-related FAQ, shelf life/allergen information included

Existing File Flow

Prompt: "Use this detail page draft to develop pricing and marketing plans" + detail page file Expected Results:

• Copy existing detail page to _workspace/02_detail_page.md
• Reverse-extract product information from the detail page to generate a planning brief
• Deploy pricing + marketing + cs agents

Error Flow

Prompt: "Prepare a product launch, but I haven't decided what to sell yet" Expected Results:

• Planner suggests 3 trend-based categories and requests user selection
• Or selects the most promising category and proceeds as an example
• Review report notes "Product undetermined — proceeded on example basis"

Agent Extension Skills