Skip to content

PD Phase 2: PRD

Create a Product Requirements Document following the VisiTrans 12-section template, informed by research and PID.

Command: /pd-2-prd [--from-brief FILE | --update]

When to use

After user research is complete and personas are defined. If a PID (Project Implementation Document) exists at 03-PRD/PID.md, the PRD will incorporate its technical constraints. If not, the skill recommends creating one first with /pd-pid.

What happens

  1. Research loading -- Reads personas from 02-Knowledge/02-Zielgruppen-Personas/ and interview analyses from 02-Knowledge/04-Dokumente/. Pre-populates pain points, feature suggestions, and user quotes.
  2. PID loading -- If 03-PRD/PID.md exists, extracts tech stack, infrastructure requirements, and security constraints for Sections 6-8.
  3. Interactive gathering -- Walks through executive summary, problem statement, personas, feature requirements, success metrics, and timeline.
  4. PRD generation -- Creates 03-PRD/PRD.md with all 12 standard sections, including the feature table with Prototyp and FB-Link columns for traceability.
  5. Validation -- Checks that all sections are complete, features have acceptance criteria, and metrics are measurable.

Modes

  • Default -- Interactive PRD creation guided by research findings
  • --from-brief FILE -- Generate PRD skeleton from an existing brief document
  • --update -- Update an existing PRD, preserving structure and incrementing version

Output

  • 03-PRD/PRD.md with 12 sections following VisiTrans template
  • Feature table linking features to prototype screens and SPECchen files
  • Quality checklist confirmation

Quality gate

  • All 12 sections complete
  • Feature table has Prototyp and FB-Link columns
  • Stakeholder sign-off obtained (Section 12)

Next step

PD Phase 3: Prototype