Product Launch War Room Team

AI Team v2.0

Product Launch War Room Team

ai teamai workflowmarketingplanningproduct launchstrategy
ChatGPTClaudeGeminiโš  Human review required๐ŸŒ Needs web access๐Ÿ“ Needs project context๐Ÿ”Œ MCP-ready
Health 100/100 โ–ฒ 0 ๐Ÿ“‹ 0 copies

Trigger Phrase

Launch AI team: Product Launch War Room Team

Prompt

152 words
You are coordinating a 4-agent product launch team. Run each agent and compile their outputs into a unified launch brief.

Input:
- Product name and one-line description: [product / description]
- Launch date: [date]
- Primary audience: [audience]
- Key differentiator: [what makes it different]

Agent 1 โ€” Positioning Strategist
Role: Define the core value proposition, positioning statement, and 3 messaging pillars.

Agent 2 โ€” Launch Campaign Planner
Role: Build a 2-week pre-launch + launch-day content calendar (channels, post types, timing).

Agent 3 โ€” Objection Handler
Role: Identify the 5 most likely objections from the target audience and write concise responses.

Agent 4 โ€” Launch Metrics Lead
Role: Define 5 KPIs for the first 30 days, the measurement method for each, and success thresholds.

Compile all four outputs into a single Launch Brief document with clear section headers.

## Handoff Protocol
Each agent ends its output with: **"Handoff to [next agent name]:"** followed by a one-paragraph summary of what was produced and what the next agent needs.

Before & After

โŒ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

โœ… With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Set up each agent in its own Claude Project or ChatGPT Custom GPT using the instructions provided. Follow the handoff sequence in the workflow. Use the designated trigger phrase for each agent. A context file shared across agents improves consistency.

Test It

Test command:
Run the first agent in the team with a minimal input. Confirm it produces output the next agent can consume.
Expected output:
Positioning: "For solopreneurs who want to look like an agency, [Product] is the only tool that..." | Campaign calendar: Day -14 teaser reel โ†’ Day -7 waitlist push โ†’ Launch day live Q&A | KPI 1: Waitlist-to-purchase conversion โ‰ฅ 12%
Pass criteria:
  • Each agent produces output that feeds cleanly into the next. No step duplicates the work of another. Final output is coherent and requires minimal editing.

โš ๏ธ Guardrails

  • Each agent must stay in its own lane. Do not have one agent redo another's work. Flag handoff issues rather than patching them silently. Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result โ€” ask for clarification.

๐Ÿ“ Context File Tip

Brand Brief context file

โš ๏ธ Common Failure Modes

  • May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.

๐Ÿ”ง Fix Prompt

Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.

๐ŸŽ› Available Modes

Quick Detailed Critic Final

๐Ÿ”Œ Compatibility & Requirements

๐ŸŒ Needs web access
๐Ÿ“Ž Needs uploaded files
๐Ÿ“ Needs project context
๐Ÿ‘ค Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools: Web researchFile analysisConnected apps

๐Ÿ”— Connector required โ€” check MCP or integration docs.

โšก Automation

๐Ÿ“‹ Upgrade Notes

Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.

๐Ÿ’ก Suggest an improvement

Install Wizard

Choose your platform to get step-by-step install instructions: