/create-prd

name: create-prd
description: Create new PRD with interactive refinement and AI assistance
category: PRD Management

Create PRD Command

Create a new Product Requirements Document with interactive questions to refine scope before generation.

Purpose

Generate well-scoped PRDs through:

• Interactive clarifying questions
• AI-assisted content generation
• Standardized structure
• Automatic ID assignment
• Draft mode by default (review later on feature branch)

Workflow

Step 0: Check for Template Usage (NEW in v2.6)

**Check for --template flag**:

/create-prd --template=ecommerce "Add shopping cart feature"

**If template specified**: 1. List available templates if `--list-templates` 2. Load template YAML file 3. Pre-fill PRD sections from template 4. Skip to Step 3 (generation)

**Available Templates** (7 total):

• 🛒 `ecommerce` - Online store with cart, checkout, payments
• 💼 `saas` - SaaS app with auth, billing, dashboard
• 📱 `mobile-app` - Cross-platform mobile with offline support
• 🔌 `api-service` - REST/GraphQL API with documentation
• ⚙️ `admin-panel` - Admin dashboard with CRUD operations
• 📊 `analytics-dashboard` - Real-time analytics and reporting
• 🔗 `integration` - Third-party API integration with webhooks

**List templates**:

/create-prd --list-templates

📋 Available PRD Templates:

1. 🛒 ecommerce - E-Commerce Store
   Online store with product catalog, cart, checkout, and payments

2. 💼 saas - SaaS Application
   SaaS app with authentication, billing, and user dashboard

3. 📱 mobile-app - Mobile Application
   Cross-platform mobile app for iOS and Android

4. 🔌 api-service - API Service
   RESTful API or GraphQL service with documentation

5. ⚙️ admin-panel - Admin Dashboard
   Internal admin panel with CRUD and user management

6. 📊 analytics-dashboard - Analytics Dashboard
   Real-time analytics and reporting dashboard

7. 🔗 integration - Third-Party Integration
   Integration with third-party API and webhooks

Usage: /create-prd --template=<name> "Your feature description"
Example: /create-prd --template=ecommerce "Add shopping cart"

**Template Benefits**:

• Pre-filled acceptance criteria (P0, P1, P2)
• Tech stack recommendations
• Out-of-scope examples (prevent creep)
• Success metrics
• Risk analysis
• 50% faster PRD creation

Step 0.5: Auto-Detect Feature Type (NEW in v0.3)

**Before generating PRD, analyze feature description for type hints**:

FEATURE_DESC="Add dark mode to the app"

# Detection logic
if echo "$FEATURE_DESC" | grep -iE "experiment|poc|prototype|test|trial|pilot" > /dev/null; then
  FEATURE_TYPE="experiment"
  TEMPLATE_FILE="product/templates/experiment.md"
  EMOJI="🧪"
elif echo "$FEATURE_DESC" | grep -iE "fix|bug|hotfix|patch|update|tweak|small|minor|quick" > /dev/null; then
  FEATURE_TYPE="quick"
  TEMPLATE_FILE="product/templates/quick-feature.md"
  EMOJI="⚡"
else
  FEATURE_TYPE="full"
  TEMPLATE_FILE="product/templates/full-feature.md"
  EMOJI="🎯"
fi

**Display detection result**:

🔍 **Feature Type Auto-Detected**: ${EMOJI} ${FEATURE_TYPE^}

Based on keywords in: "${FEATURE_DESC}"

Detected as: **${FEATURE_TYPE^} Feature**
- Template: ${TEMPLATE_FILE}
- Estimated: ${ESTIMATE}

Is this correct? (y/n/change)
> _

**Type characteristics**:

| Type | Keywords | Estimate | Template | |------|----------|----------|----------| | 🎯 Full | (default) | 5+ days | full-feature.md | | ⚡ Quick | fix, bug, update, small | 1-3 days | quick-feature.md | | 🧪 Experiment | experiment, poc, prototype | 1-2 weeks | experiment.md |

**If user says "change"**:

Which type should this be?
  [1] 🎯 Full Feature (5+ days)
  [2] ⚡ Quick Ship (1-3 days)
  [3] 🧪 Experiment/POC (1-2 weeks)

Choose: _

**Why this matters**:

• **Different templates** for different feature sizes
• **Right level of detail** - Quick features don't need extensive docs
• **Clearer expectations** - Team knows scope upfront

Step 1: Gather Feature Description

Ask user for brief feature description:

What feature do you want to build?

Example: "Add OAuth2 authentication with Google and GitHub"

💡 Tip: Use --template flag for faster PRD creation!
   /create-prd --list-templates

> [User input]

Step 2: Detect Feature Type & Ask Contextual Questions

**NEW**: AI detects feature type and asks **type-specific questions** instead of generic ones.

Step 2a: Classify Feature Type

AI analyzes description and classifies into one of these types:

• 🔐 **Authentication/Security** (login, OAuth, permissions, encryption)
• 💳 **Payment/Financial** (billing, subscriptions, invoices, PCI)
• 🎨 **UI/UX** (design, themes, layouts, components)
• 🔌 **API/Backend** (endpoints, services, data processing)
• 🗄️ **Database** (schema, migrations, data modeling)
• 🔗 **Integration** (third-party APIs, webhooks, SDKs)
• 🏗️ **Infrastructure** (CI/CD, deployment, monitoring)
• 📊 **Analytics/Reporting** (dashboards, metrics, exports)
• 🧪 **Testing/QA** (test frameworks, coverage, automation)
• 📝 **Simple/Generic** (unclear type or very simple)

Step 2b: Ask Type-Specific Questions (4-6 questions)

**For simple/well-defined features**: Skip questions, go straight to generation **For complex features**: Ask targeted questions based on type

**Question Selection Strategy** (Enhanced):

Great! Let me ask a few questions to refine the scope...

Question 1: Target Users
Who will use this feature?
Options:
- All users (B2C)
- Enterprise/B2B users only
- Internal team/developers
- Specific user segment

> [User answers]

Question 2: Core Requirements
What are the 2-3 must-have capabilities for v1?
(Focus on minimum viable scope)

> [User lists core requirements]

Question 3: Out of Scope
What are you explicitly NOT doing in v1?
(This prevents scope creep - be specific!)

> [User defines boundaries]

Question 4: Integration Points (if applicable)
Does this integrate with existi