create-prd-env

Create PRD Environment Command

Initialize the complete PRD workflow structure in any project with one command.

Purpose

Set up everything needed for PRD-driven development:

• Folder structure (01-draft → 04-complete)
• PRD templates (full, quick, experiment)
• Configuration files
• Documentation
• Decision log

Use cases:

• New project starting from scratch
• Existing project adopting PRD workflow
• Migrate from old PRD structure (v2.x → v0.3)

Workflow

Step 1: Detect Existing Structure

Check for existing PRD folders:

# Check for old v2.x structure
if [ -d "product/prds/02-review" ]; then
  echo "⚠️ Old structure detected (v2.x)"
  echo "Migration needed: 02-review → removed"
  echo "                  03-ready → 02-ready"
  echo "                  04-in-progress → 03-in-progress"  
  echo "                  05-complete → 04-complete"
fi

# Check if already initialized
if [ -f "product/.prd-config.json" ]; then
  echo "ℹ️ PRD environment already initialized"
  echo "Version: $(cat product/.prd-config.json | grep version)"
fi

If existing found, ask user:

📦 Existing PRD Structure Found

Options:
  [1] Migrate to v0.3.0 structure (recommended)
  [2] Clean install (backup existing)
  [3] Validate existing structure
  [4] Cancel

Choose: _

If none found, proceed to create.

Step 2: Create Folder Structure

# Create PRD folders (v0.3 structure)
mkdir -p product/prds/{01-draft,02-ready,03-in-progress,04-complete,99-archived}

# Create supporting folders
mkdir -p product/decisions
mkdir -p product/templates

echo "✅ Folder structure created"

Structure:

product/
├── prds/
│   ├── 01-draft/         # New PRDs
│   ├── 02-ready/         # Ready to code
│   ├── 03-in-progress/   # Being implemented
│   ├── 04-complete/      # Merged to production
│   └── 99-archived/      # Historical reference
├── decisions/            # Architecture Decision Records
├── templates/            # PRD templates
└── WORK_PLAN.md          # Pipeline tracker