Workshopping PRDs

Interactive product requirements document creation with structured phases.

Usage

code

/workshopping-prds [options]

Options

•--template TEMPLATE: PRD template (full|lean|technical)
•--output PATH: Output file path
•--from-item ID: Start from existing work item
•--quick: Skip optional sections

Examples

bash

# Full interactive session
/running-prd-sessions

# Start from existing idea
/running-prd-sessions --from-item CCC-123

# Quick lean PRD
/running-prd-sessions --template lean --quick

# Technical PRD
/running-prd-sessions --template technical

Session Phases

Phase 1: PM Mode - Problem Discovery

Objective: Understand the problem space

markdown

## Problem Discovery

Let's understand what we're solving.

❓ What problem are we trying to solve?
>

❓ Who experiences this problem?
>

❓ How do they currently deal with it?
>

❓ Why is now the right time to solve this?
>

❓ What happens if we don't solve it?
>

Output: Problem statement, user personas, opportunity assessment

Phase 2: Architect Mode - Solution Space

Objective: Explore solution approaches

markdown

## Solution Exploration

Now let's think about solutions.

❓ What are possible approaches to solve this?
>

❓ What's the simplest version that could work?
>

❓ What technical constraints exist?
>

❓ What similar solutions exist in the market?
>

❓ What's our unique angle?
>

Output: Solution options, technical feasibility, differentiation

Phase 3: PO Mode - Requirements Definition

Objective: Define what we're building

markdown

## Requirements Definition

Let's get specific about what we're building.

### User Stories

❓ Complete this: "As a [user], I want [capability], so that [benefit]"
> (repeat for 3-5 primary stories)

### Acceptance Criteria

For each user story:
❓ How will we know it's working correctly?
>

### Scope Boundaries

❓ What's explicitly OUT of scope?
>

❓ What's nice-to-have vs must-have?
>

Output: User stories, acceptance criteria, scope definition

Phase 4: SWE Mode - Technical Planning

Objective: Plan implementation approach

markdown

## Technical Planning

Now let's think about how to build it.

❓ What are the main technical components?
>

❓ What existing systems does this integrate with?
>

❓ What new infrastructure is needed?
>

❓ What are the biggest technical risks?
>

❓ How would you break this into phases?
>

Output: Technical architecture, integration points, risk assessment

Phase 5: Synthesis - Document Generation

Compile all inputs into structured PRD:

markdown

# PRD: {Product/Feature Name}

## Executive Summary
{Generated from Phase 1}

## Problem Statement
### Current State
{From Phase 1}

### Desired State
{From Phase 2}

### Success Metrics
{Derived from acceptance criteria}

## User Personas
{From Phase 1}

## Solution Overview
{From Phase 2}

## Detailed Requirements

### User Stories
{From Phase 3}

### Acceptance Criteria
{From Phase 3}

### Non-Functional Requirements
{From Phase 4}

## Technical Approach
{From Phase 4}

## Scope
### In Scope
{From Phase 3}

### Out of Scope
{From Phase 3}

## Risks & Mitigations
{From Phase 4}

## Timeline & Phases
{From Phase 4}

## Appendix
{Any additional details}

Templates

Full Template

All sections, comprehensive documentation. Best for: Major features, new products, cross-team initiatives.

Lean Template

Core sections only: Problem, Solution, Requirements, Scope. Best for: Smaller features, internal tools, quick iterations.

Technical Template

Focus on architecture, integration, implementation. Best for: Infrastructure changes, API design, technical debt.

Output Options

•Markdown file - Save to docs/
•Work item - Create epic via pm-context
•Both - File + linked work item

Session Tips

•Answer questions conversationally, not formally
•It's OK to say "I don't know yet"
•Revisit earlier sections if needed
•Ask clarifying questions back
•Use examples to illustrate points

Example Session

code

🚀 Starting PRD Session

Template: Full
Output: docs/prd-user-notifications.md

━━━ Phase 1: Problem Discovery ━━━

❓ What problem are we trying to solve?
> Users miss important updates because we have no notification system

❓ Who experiences this problem?
> All users, but especially power users who manage multiple projects

...

━━━ Phase 5: Generating PRD ━━━

✅ PRD generated: docs/prd-user-notifications.md

Would you like to:
1. Create an epic from this PRD
2. Refine any section
3. Done

>