# PRD Management configuration template - docs/prd_management.yaml
kind: prd_management
version: "1"
updated_at: "{{ today }}"

# PRD Configuration
enabled: {{ prd_management.enabled | default(true) }}
prd_file: "{{ prd_management.prd_file | default('docs/PRD.md') }}"

# Purpose
purpose:
  - "Recording original requirements: Preserve user's initial requirement descriptions"
  - "Tracking requirement changes: Record how requirements evolve through dialogue"
  - "Requirement traceability: Understand the complete journey from proposal to implementation"
  - "Requirement statistics: Overview of requirement status distribution"

# Requirement Structure
requirement_structure:
  fields:
    - name: "id"
      description: "REQ-001, REQ-002, ..."
      required: true
    - name: "title"
      description: "Concise requirement name"
      required: true
    - name: "original_description"
      description: "User's initial requirement description"
      required: true
    - name: "current_description"
      description: "Refined description after clarification"
      required: true
    - name: "status"
      description: "draft / confirmed / in_progress / completed / cancelled"
      required: true
    - name: "priority"
      description: "high / medium / low"
      required: true
    - name: "created_at"
      description: "When the requirement was first recorded"
      required: true
    - name: "updated_at"
      description: "When the requirement was last modified"
      required: true
    - name: "change_history"
      description: "Record of requirement description changes"
      required: false
    - name: "related_tasks"
      description: "Associated TASK-IDs"
      required: false

# Status Flow
status_flow:
  - "draft -> confirmed -> in_progress -> completed"
  - "draft -> cancelled"
  - "in_progress -> cancelled"

# Usage Flow
usage_flow:
  proposal_phase:
    - "User proposes requirement in dialogue"
    - "AI uses requirement clarification protocol"
    - "Creates new requirement entry in PRD"
  evolution_phase:
    - "Further define requirement details in dialogue"
    - "Update current description and change history"
    - "Update requirement status"
  implementation_phase:
    - "Update requirement status to in_progress"
    - "Update to completed when done"
    - "Record associated TASK-ID"

# Trigger Words
trigger_words:
  - "record requirement"
  - "update PRD"
  - "view requirements"
  - "requirement status"
  - "PRD"
  - "requirements document"

# Update Timing
update_timing:
  - "When new requirement is proposed: Create new requirement entry"
  - "After requirement clarification: Update description and history"
  - "When requirement status changes: Update the status field"
  - "When requirement implementation completes: Update status, associate TASK-ID"

# Best Practices
best_practices:
  original_description: "Keep user's exact words, no modification"
  current_description: "Structured description after clarification"
  change_reason: "Clearly explain why the requirement changed"
