vt-c-pd-2-prd

Create a Product Requirements Document with PID reference for a project following VisiTrans template structure.

Plugin: core-standards
Category: Product Design Workflow
Command: /vt-c-pd-2-prd

---

Product Design: PRD Creation

Create comprehensive Product Requirements Documents (PRDs) that capture requirements, user needs, and success criteria for development handoff.

Workflow Position

/vt-c-pd-0-start → /vt-c-pd-1-research → /vt-c-pd-pid → /vt-c-pd-2-prd → /vt-c-pd-3-prototype → /vt-c-pd-4-validate → /vt-c-pd-6-handoff → /vt-c-activate
                                           │
                                           └── You are here
                                               Inputs: Personas, PID

Invocation

/vt-c-pd-2-prd                      # Interactive PRD creation
/vt-c-pd-2-prd --from-brief FILE    # Generate from existing brief
/vt-c-pd-2-prd --update             # Update existing PRD

Configuration

# Project template structure (OneDrive)
project_template: "ONEDRIVE_ROOT/02-Projekte/00-projektvorlage"
output_path: "03-PRD/PRD.md"
pid_path: "03-PRD/PID.md"
personas_path: "02-Knowledge/02-Zielgruppen-Personas/"
research_path: "02-Knowledge/04-Dokumente/"

Iteration Loop Integration

Step 0: Check Design State (Before Starting)

Before beginning PRD work, check the design state:

# Load design state
Read: .design-state.yaml

# Check for pending inbox items
if inbox.pending_items exists:
  Run: /vt-c-pd-inbox-scan to process first

If this is an iteration (returning to PRD):

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Iteration Context: pd-2-prd
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Returning to PRD phase (Iteration {n})

Trigger: {trigger from state file}
Reason: {reason from state file}

Previous PRD version: {artifacts.prd.version}
Changes needed:
• {items from iteration trigger}

Focus: Update PRD.md Sections affected by changes
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Quality Gate: pd-2-prd

Mark phase as complete when: - [ ] All 12 PRD sections complete - [ ] Feature table has Prototyp and FB-Link columns - [ ] Stakeholder sign-off obtained (Section 12) - [ ] Links to personas and research valid

Update state file on completion:

quality_gates:
  pd-2-prd:
    passed: true
    passed_at: "{timestamp}"
    criteria:
      all_sections_complete: true
      stakeholder_review: true
      features_prioritized: true

artifacts:
  prd:
    version: "{increment}"
    hash: "{compute md5}"
    status: "approved"

---

Execution Instructions

Step 1: Detect Project Context

1. Check current working directory for project structure
2. Look for existing files:
3. 03-PRD/PRD.md - Existing PRD to update
4. 03-PRD/PID.md - Technical constraints document
5. 02-Knowledge/ - Research materials
6. 02-Knowledge/02-Zielgruppen-Personas/ - User personas

7. 02-Knowledge/04-Dokumente/interview-analysis-*.md - Interview findings

8. Display context:

   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   PRD Creation - Product Design Phase 2
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   
   Project: [directory name]
   Output: 03-PRD/PRD.md
   
   Research Inputs:
   [✓/✗] User personas from /vt-c-pd-1-research
   [✓/✗] Interview analyses
   [✓/✗] PID.md (tech constraints)
   [✓/✗] Existing PRD (for update)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   

Step 2: Load Research Findings

Load from /vt-c-pd-1-research outputs:

1. Read personas from 02-Knowledge/02-Zielgruppen-Personas/
2. Read interview analyses from 02-Knowledge/04-Dokumente/interview-analysis-*.md
3. Extract:
4. Pain points identified
5. Unmet needs
6. Feature suggestions
7. Quotes for validation

Display:

Research Findings Loaded:
─────────────────────────────────────────────────────────────────
Personas: [N] defined
  • [Persona 1] - [brief description]
  • [Persona 2] - [brief description]

Interview Analyses: [N] processed
  • Key pain points: [list]
  • Feature requests: [list]
  • Unmet needs: [list]

Step 3: Load Technical Constraints (PID)

If 03-PRD/PID.md exists: 1. Read the PID document 2. Extract: - Target tech stack (frontend, backend, database) - Infrastructure requirements - Integration constraints - Security requirements - Performance expectations

1. Display summary:

   Technical Constraints (from PID):
   ─────────────────────────────────────────────────────────────────
   • Frontend: [framework]
   • Backend: [framework]
   • Database: [type]
   • Key constraints: [list]
   

If 03-PRD/PID.md does NOT exist:

⚠ No PID found at 03-PRD/PID.md

The PID (Project Implementation Document) defines the technical
architecture, stack, and constraints that inform PRD sections
6 (Integrations), 7 (Data Models), and 8 (Non-Functional Requirements).

Recommendation: Run /vt-c-pd-pid first to create the PID.
You can also continue without it and create the PID later.

Use AskUserQuestion: - "Create PID now with /vt-c-pd-pid (Recommended)" -- technical constraints will inform the PRD - "Continue without PID" -- create PRD first, add technical details later

Step 4: Gather Requirements (Interactive Mode)

If no --from-brief provided, guide through requirements gathering:

4a. Executive Summary

What is this product/feature in one paragraph?
(Target audience, main purpose, key value proposition)

4b. Problem Statement

What problem are we solving?
(Pre-populated from interview findings if available)
- Who has this problem? [from personas]
- What is the current state? [from interviews]
- What is the desired state?
- Why does this matter?

4c. User Personas

Personas from research:
─────────────────────────────────────────────────────────────────
1. [Persona 1] - [description]
   Pain points: [from research]
   Key quote: "[quote from interview]"

2. [Persona 2] - [description]
   Pain points: [from research]
   Key quote: "[quote from interview]"

Use these personas? [Y/n]
Add new persona? [y/N]

4d. Feature Requirements

Features identified from research:
─────────────────────────────────────────────────────────────────
• [Feature from interviews]
• [Feature from interviews]

Additional features to add? (one per line)
- Feature 1: [description]
- Feature 2: [description]

For each feature, specify:
- Priority (Must-have / Should-have / Nice-to-have)
- User story format: "As a [persona], I want to [action] so that [benefit]"

4e. Success Metrics

How will we measure success?
- Metric 1: [target]
- Metric 2: [target]

4f. Timeline/Phases

What is the delivery timeline?
- Phase 1: [scope] - [date]
- Phase 2: [scope] - [date]

Step 5: Generate PRD Document

Create 03-PRD/PRD.md using the standard 12-section VisiTrans template.

PRD Template Structure (12 sections):

# Product Requirements Document

**Project**: [Name]
**Version**: 1.0
**Date**: [YYYY-MM-DD]
**Author**: [Name]
**Status**: Draft

---

## 1. Projekt-Übersicht (Project Overview)

### Kurzbeschreibung
[One paragraph overview]

### Strategische Business-Ziele
[Business goals and KPIs]

### Zeitrahmen
[Timeline and milestones]

---

## 2. Problemstellung & Kontext

### Welches Problem lösen wir?
[Description with quotes from user research]

### Für wen lösen wir es?
[Target users - link to personas]

### Status Quo
[Current state and workarounds]

---

## 3. Lösungsvision

### Beschreibung der Lösung
[High-level solution description]

### User Journeys
[Key user flows]

### Erfolgskriterien & KPIs
[Success metrics]

---

## 4. Features (High-Level)

| # | Feature-Name | Kurzbeschreibung | Priorität | Status | Prototyp | FB-Link |
|---|--------------|------------------|-----------|--------|----------|---------|
| 1 | [Feature 1] | [description] | Must-Have | ☐ Backlog | [link] | spec-1 |
| 2 | [Feature 2] | [description] | Should-Have | ☐ Backlog | [link] | spec-2 |

---

## 5. Scope & Abgrenzung

### ✅ Im Scope
[What is included]

### ❌ Nicht im Scope
[What is explicitly excluded]

---

## 6. System-Integrationen & Abhängigkeiten

| System | Daten | Richtung | Häufigkeit |
|--------|-------|----------|------------|
| [System] | [Data] | In/Out | [Frequency] |

---

## 7. Data Models & Schema

### Neue Entitäten
| Entity | Beschreibung | Attribute | Beziehungen |
|--------|--------------|-----------|-------------|
| [Entity] | [Desc] | [Attrs] | [Relations] |

---

## 8. Nicht-funktionale Anforderungen

### Performance
[Performance requirements from PID]

### Sicherheit & Compliance
[Security requirements from PID]

### Testing-Strategie
[Test approach]

---

## 9. Implementierungsplanung

### Entwicklungspakete
[Link to specs files once created]

### Definition of Ready
[Handoff checklist]

### Definition of Done
[Completion criteria]

---

## 10. Risiken & offene Fragen

### Bekannte Risiken
| Risiko | Wahrscheinlichkeit | Impact | Mitigation |
|--------|-------------------|--------|------------|
| [Risk] | Hoch/Mittel/Niedrig | [Impact] | [Mitigation] |

### Offene Fragen
- [ ] Question 1
- [ ] Question 2

---

## 11. Anhänge & Referenzen

### Design & UX
- Prototype: [04-prototyp/ link]
- Figma: [link]

### User Research
- Personas: [02-Knowledge/02-Zielgruppen-Personas/]
- Interview analyses: [02-Knowledge/04-Dokumente/]

### Technical
- PID: [03-PRD/PID.md]

---

## 12. Stakeholder Review & Freigabe

| Name | Rolle | Datum | Freigabe |
|------|-------|-------|----------|
| [Name] | [Role] | [Date] | ☐ Pending |

### Änderungshistorie
| Version | Datum | Autor | Änderungen |
|---------|-------|-------|------------|
| 1.0 | [date] | [author] | Initial version |

Step 6: From Brief Mode (--from-brief)

If --from-brief FILE is specified: 1. Read the brief/requirement document 2. Extract key information automatically 3. Generate PRD skeleton 4. Prompt for missing information

Step 7: Update Mode (--update)

If --update is specified: 1. Read existing 03-PRD/PRD.md 2. Preserve structure and existing content 3. Allow section-by-section updates 4. Increment version number 5. Add change log entry

Step 8: Validation and Summary

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PRD Created Successfully
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Document: 03-PRD/PRD.md
Version: 1.0

Summary:
─────────────────────────────────────────────────────────────────
• Features: X total (Y must-have, Z should-have)
• Personas: N referenced from research
• Success metrics: M defined
• Phases: P planned

Quality Checklist:
[✓/✗] Executive summary present
[✓/✗] Problem statement with research backing
[✓/✗] User personas from /vt-c-pd-1-research
[✓/✗] Features have acceptance criteria
[✓/✗] Feature table has Prototyp and FB-Link columns
[✓/✗] Success metrics measurable
[✓/✗] Technical constraints from PID

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NEXT STEPS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

1. Review PRD with stakeholders
2. Create prototype: /vt-c-pd-3-prototype
3. Validate with users: /vt-c-pd-4-validate
4. Development handoff: /vt-c-pd-6-handoff
5. Generate specs from PRD: /vt-c-activate --from-prd
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 8.5: User Manual Prompt

After displaying the summary, check if docs/user-manual/ exists. If it does NOT exist, prompt:

Use AskUserQuestion: - Generate user manual (Recommended) — runs /vt-c-user-manual-generate with the PRD just created - Skip for now — continue without generating; can run /vt-c-user-manual-generate manually later

If docs/user-manual/ already exists: skip this prompt silently.

Integration with Product Design Workflow

The PRD is created in Phase 2 of Product Design: 1. /vt-c-pd-0-start - Initialize project structure 2. /vt-c-pd-1-research - Gather user research, create personas 3. /vt-c-pd-2-prd - Create PRD using research findings ← YOU ARE HERE 4. /vt-c-pd-3-prototype - Generate prototype from PRD 5. /vt-c-pd-4-validate - Test prototype with users 6. /vt-c-pd-6-handoff - Hand off to development 7. /vt-c-activate --from-prd - Generate specs from PRD

PID Reference

The Project Implementation Document (PID) provides technical context: - Tech stack decisions - Architecture patterns - Database schema guidelines - API specifications - Security requirements

When a PID exists, the PRD automatically incorporates technical constraints to ensure requirements are feasible for development.

Feature Table Format

The feature table in Section 4 is critical for tracking:

Column	Purpose
#	Feature number for reference
Feature-Name	Unique identifier
Kurzbeschreibung	1-sentence description
Priorität	Must-Have / Should-Have / Nice-to-Have
Status	☐ Backlog / ☐ Doing / ☑️ Done / ☐ Testing
Prototyp	Link to Figma or prototype screen
FB-Link	Link to spec file (filled by /vt-c-activate --from-prd)

This table connects PRD → Prototype → Specs for traceability.

Open Brain Capture (Optional)

After creating or updating the PRD, if the capture_thought MCP tool is available, capture the PRD executive summary.

When to capture: After every finalized PRD creation or major update.

How: 1. Check if capture_thought tool is available. If not: skip silently. 2. Call capture_thought with:

thought: "PRD created: {product name}. Vision: {1-sentence vision}. Target users: {personas}. Key features: {top 3-5 features}. Success metrics: {primary KPIs}."

3. On timeout or error: log debug message and continue. Never fail the skill.