vt-c-kw-prd

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

Plugin: core-standards
Category: Knowledge Work Workflow
Command: /vt-c-kw-prd

---

Knowledge Work: PRD Creation

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

Workflow Position

/vt-c-kw-0-start  →  /vt-c-kw-1-plan  →  /vt-c-kw-2-execute  →  /kw-review  →  /kw-publish
                              │
                              ▼
                         /vt-c-kw-prd ◄── Create PRD here
                              │
                              ▼
                       /vt-c-kw-specs (break into features)

Invocation

/vt-c-kw-prd                      # Interactive PRD creation
/vt-c-kw-prd --from-brief FILE    # Generate from existing brief
/vt-c-kw-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"

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. Display context:

   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   PRD Creation
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   
   Project: [directory name]
   Output: 03-PRD/PRD.md
   
   Detected:
   [✓/✗] PID.md (tech constraints)
   [✓/✗] Existing PRD
   [✓/✗] User personas
   [✓/✗] Research materials
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   

Step 2: 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]
   

Step 3: Gather Requirements (Interactive Mode)

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

3a. Executive Summary

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

3b. Problem Statement

What problem are we solving?
- Who has this problem?
- What is the current state?
- What is the desired state?
- Why does this matter?

3c. User Personas

Check for existing personas in 02-Knowledge/02-Zielgruppen-Personas/:

Found personas:
1. [Persona 1] - [description]
2. [Persona 2] - [description]

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

3d. Feature Requirements

List the key features (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]"

3e. Success Metrics

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

3f. Timeline/Phases

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

Step 4: Generate PRD Document

Create 03-PRD/PRD.md with structure:

# Product Requirements Document

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

---

## Executive Summary

[One paragraph overview]

---

## Problem Statement

### Current State
[Description of current pain points]

### Desired State
[Description of target experience]

### Why This Matters
[Business impact and user benefit]

---

## User Personas

### Primary Persona: [Name]
- **Role**: [role]
- **Goals**: [goals]
- **Pain Points**: [frustrations]
- **Context**: [usage context]

### Secondary Persona: [Name]
[Similar structure]

---

## Feature Requirements

### Must-Have (P0)

#### Feature 1: [Name]
- **User Story**: As a [persona], I want to [action] so that [benefit]
- **Acceptance Criteria**:
  - [ ] Criterion 1
  - [ ] Criterion 2
- **Technical Notes**: [from PID if applicable]

### Should-Have (P1)

[Similar structure]

### Nice-to-Have (P2)

[Similar structure]

---

## Success Metrics

| Metric | Current | Target | Measurement Method |
|--------|---------|--------|-------------------|
| [Metric 1] | [value] | [value] | [how to measure] |
| [Metric 2] | [value] | [value] | [how to measure] |

---

## Technical Constraints

*Extracted from PID.md*

- **Tech Stack**: [stack]
- **Performance**: [requirements]
- **Security**: [requirements]
- **Integration**: [requirements]

---

## Timeline

| Phase | Scope | Target Date | Dependencies |
|-------|-------|-------------|--------------|
| Phase 1 | [MVP scope] | [date] | - |
| Phase 2 | [Extended scope] | [date] | Phase 1 |

---

## Open Questions

- [ ] Question 1
- [ ] Question 2

---

## Appendix

### Related Documents
- PID: [link to PID.md]
- Research: [link to 02-Knowledge]
- Personas: [link to persona docs]

### Change Log
| Version | Date | Author | Changes |
|---------|------|--------|---------|
| 1.0 | [date] | [author] | Initial version |

Step 5: 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 6: 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 7: 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 defined
• Success metrics: M defined
• Phases: P planned

Quality Checklist:
[✓/✗] Executive summary present
[✓/✗] Problem statement clear
[✓/✗] User personas defined
[✓/✗] Features have acceptance criteria
[✓/✗] Success metrics measurable
[✓/✗] Technical constraints from PID

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

1. Review PRD with stakeholders
2. Create prototype: /vt-c-kw-prototype
3. Break into feature briefs: /vt-c-kw-specs
4. Conduct user research: /vt-c-kw-user-test

For large PRDs, generate specs (feature briefs) before handoff
to development team.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Integration with Knowledge Work Workflow

The PRD is typically created during /vt-c-kw-2-execute phase: 1. Use /vt-c-kw-0-start to initialize project 2. Use /vt-c-kw-1-plan to define approach 3. Use /vt-c-kw-prd within /vt-c-kw-2-execute to create requirements 4. Follow with /vt-c-kw-prototype and /vt-c-kw-specs

PID Reference

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

Example PID location: <project-root>/.specify/memory/PID.md

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