explore-prd

Explore PRD Command

Lightweight exploration of feature ideas before committing to full PRD.

Purpose

Validate feature ideas early:

• Quick problem validation
• Solution brainstorming
• Effort estimation
• Go/No-Go decision
• Lightweight documentation

Workflow

1. Problem Definition

Capture initial idea:

• User pain point
• Current workaround
• Frequency and impact
• Evidence (if available)

Example:

🔍 Exploring: Export to PDF

Problem: Users can't share reports offline
Current: Screenshots or manual copy-paste
Frequency: ~20 requests/month
Impact: Medium (workaround exists)

2. Solution Brainstorming

Generate alternatives:

• Approach A: Build custom PDF generator
• Approach B: Use third-party service (e.g., PDFKit)
• Approach C: Browser print-to-PDF
• Approach D: Export to Google Docs, then PDF

Quick pros/cons for each.

3. Rough Effort Estimate

T-shirt sizing:

• S (1-2 days)
• M (3-5 days)
• L (1-2 weeks)
• XL (2+ weeks)

Include:

• Development time
• Testing time
• Documentation time

4. Competitive Check

Quick research:

• What do competitors do?
• Industry standard approach?
• Open source libraries available?

5. Decision Point

Three outcomes:

1. GO → Create PRD:

   • Problem validated
   • Solution promising
   • Effort acceptable
   • Action: /create-prd with exploration as input

2. DEFER:

   • Good idea but not now
   • Timing not right
   • Action: Save in .prds/ideas/ for later

3. KILL:

   • Not worth doing
   • Better alternatives exist
   • Action: Document reasoning, close exploration

6. Document Exploration

Save exploration to .prds/explorations/YYYY-MM-DD-feature-name.md:

# Exploration: Feature Name

**Date**: YYYY-MM-DD
**Status**: Go/Defer/Kill

## Problem
{What user pain we're solving}

## Solutions Considered
1. Approach A: {pros/cons}
2. Approach B: {pros/cons}

## Recommended Approach
{Which solution to pursue and why}

## Effort
{T-shirt size with rough breakdown}

## Decision
{Go/Defer/Kill with reasoning}

## Next Steps
{What to do next}