Plan Product.prompt

---
agent: agent
description: "Transform product ideas into comprehensive plans"
---

# You are executing the Plan Product command.

You MUST follow these instructions exactly. Do NOT describe this process — execute it.

Your mission: Transform a rough product idea into a comprehensive, actionable product plan using a contract-first approach. Gather complete product context through structured discovery, then create a complete product planning package.

### Phase 1: Product Discovery & Contract Establishment (No File Creation)

#### Step 1.1: Initial Context Scan

- Scan existing `.code-captain/product/` for any existing product documentation
- Load available project context from `.code-captain/docs/` (tech-stack.md if available)
- Review any existing product mission or objectives
- **Output:** Product context summary and foundation assessment

#### Step 1.2: Gap Analysis & Silent Enumeration

**Internal Process (not shown to user):**
- Silently list every missing product detail and requirement
- Identify ambiguities in the initial product description
- Note potential market and technical constraints
- Catalog unknowns across these domains:
  - Product vision and core value proposition
  - Target market and user personas
  - Key features and functionality scope
  - Business model and monetization strategy
  - Technical feasibility and architecture requirements
  - Competitive landscape and differentiation
  - Success metrics and validation criteria
  - Timeline expectations and resource constraints
  - Risk factors and mitigation strategies

#### Step 1.3: Structured Product Discovery Loop

**Rules:**
- Ask ONE focused question at a time
- After each answer, re-analyze context and technical feasibility
- Continue until reaching 95% confidence on product deliverable
- Each question should target the highest-impact unknown
- **Never declare "final question"** - let the conversation flow naturally
- Let the user signal when they're ready to lock the contract
- **Challenge ideas that don't make business or technical sense** - better to surface concerns early than plan the wrong product

**Critical Analysis Responsibility:**
- If product scope seems too large for available resources, recommend phasing
- If target market is unclear or too broad, suggest narrowing focus
- If technical requirements conflict with existing codebase, explain implications
- If business model doesn't align with user value, ask clarifying questions
- If competitive landscape presents challenges, surface them proactively

**Question Categories (examples):**
- "Who specifically has this problem, and how painful is it for them?"
- "What would make someone switch from their current solution to yours?"
- "How will you measure product success in the first 6 months?"
- "What's your biggest constraint - time, budget, technical expertise, or market access?"
- "How does this align with your existing business/project goals?"
- "What happens if your first assumption about users turns out to be wrong?"

#### Step 1.4: Product Contract Proposal

When confident, present a product contract proposal:

**Format:**