---

name: prd-spec description: PRD workflow for building products from idea to implementation. Use when (1) starting a new product, (2) creating PRD documentation, (3) generating BDD scenarios, (4) building UI specs, (5) TDD implementation. Guides through 18-step process: PRD -> BDD -> UI -> TDD.

PRD-Spec Workflow

A comprehensive workflow for building products from idea to implementation through structured phases.

Quick Start

Copy# Standard workflow (new products)
/prd-spec                    # Check state, run next step
/prd-spec status             # Show progress only
/prd-spec init "My App"      # Start with product description
/prd-spec bdd-scenarios      # Jump to specific step
/prd-spec redo prd-init      # Re-run a completed step
/prd-spec verify US-001-S01  # Verify specific scenario
/prd-spec export             # Concatenate all PRD files into one document

# Import workflow (existing complete PRDs)
/prd-spec import             # Import from PRD-COMPLETE.md or PRD.md
/prd-spec import docs/other/Complete.md  # Import from specific path
/prd-spec import --dry-run   # Preview without writing files
/prd-spec import --force     # Overwrite existing files

# Backfill workflow (existing codebases)
/prd-spec backfill           # Start backfill from current directory
/prd-spec backfill ./src     # Backfill from specific path
/prd-spec backfill validate  # Human validation gate (after draft)
/prd-spec backfill skip      # Skip to Phase 1 with current state

Invocation Patterns

Workflow Phases

Phase 0: Backfill (Optional - for existing codebases)

Key Principle: Code shows BEHAVIOR, not INTENT. Human validation required.

Phase 1: PRD (10 steps)

Phase 2: BDD & UI (5 steps)

Phase 3: TDD (3 steps)

Alternative: Use /build-it skill After generating features-manifest.json in Phase 2, you can use the standalone /build-it skill for TDD implementation. It provides:

• Smart scenario selection based on priority and dependencies
• Automated RED-GREEN-REFACTOR cycle
• Automatic manifest updates when scenarios pass
• Run /build-it status to see progress

State Management

Progress tracked in docs/prd/.prd-workflow-state.json. See references/workflow-state.md for full details.

State is determined by:

1. Reading state file if exists
2. Falling back to file existence checks (PRD.md, scenarios.md, etc.)
3. Creating state file on first step

Execution Instructions

When the user invokes /prd-spec:

1. Parse Arguments - Determine action: next, status, step, redo, backfill
2. Check/Create State - Read docs/prd/.prd-workflow-state.json or create if missing
3. Determine Next Step - Use getNextStep(state) logic from references/workflow-state.md
4. Execute Step:
   • Read prompt from references/prompts/{step-name}.md
   • Replace $ARGUMENTS with any provided arguments
   • If arguments required but not provided, ask the user
   • Execute the prompt instructions
   • Update state file on completion

Step Prompts

Phase 0: Backfill

Phase 1-3: Standard

Arguments

If required arguments not provided, prompt the user.

Output Files

The PRD is organized into 4 logical files to manage token limits:

Copydocs/prd/
├── PRD.md                # Summary + Meta (~8K tokens)
│   ├── Section 1: Executive Summary
│   ├── Section 2: Goals and Success Metrics
│   ├── Section 11: MVP Scope
│   ├── Section 12: Risks and Mitigations
│   ├── Section 13: Timeline and Milestones
│   └── Section 14: Open Questions
│
├── product-vision.md     # The "What" (~15K tokens)
│   ├── Section 3: User Personas
│   ├── Section 4: Epics and User Stories
│   └── Section 5: User Journeys
│
├── requirements.md       # The "Criteria" (~20K tokens)
│   ├── Section 6: Functional Requirements
│   └── Section 7: Non-Functional Requirements
│
├── technical-spec.md     # The "How" (~30K tokens)
│   ├── Section 8: Technical Architecture
│   ├── Section 9: Data Model
│   └── Section 10: API Specifications
│
├── scenarios.md          # BDD Scenarios (Phase 2)
├── UI_SPEC.md            # UI Specification (Phase 2)
└── .prd-workflow-state.json  # Workflow state

Export Command

Use /prd-spec export to create a single PRD-COMPLETE.md by concatenating:

1. PRD.md
2. product-vision.md
3. requirements.md
4. technical-spec.md

This is useful for sharing with stakeholders who want one document.

References

• State Management: references/workflow-state.md - Full state format, step names, getNextStep() logic
• Example Sessions: references/examples.md - Standard and backfill workflow examples
• Step Prompts: references/prompts/*.md - Individual step instructions