template:
  id: prd-template-v3-enhanced
  name: VC-SYS Enhanced Product Requirements Document
  version: 3.0
  output:
    format: markdown
    filename: docs/prd.md
    title: "{{project_name}} Product Requirements Document (PRD)"

# VC-SYS Enhancement: Agent permissions and evidence requirements
permissions:
  owner: product-owner
  editors: [scrum-master, ux-expert, technical-architect]
  viewers: [developer, qa, devops]
  evidence-required: true
  anti-hallucination: enabled
  stakeholder-validation: required
  market-research: recommended

workflow:
  mode: interactive
  elicitation: advanced-elicitation
  facilitation: laboratory-agent
  validation: pm-checklist
  stakeholder-review: required
  
# VC-SYS Enhancement: Integration with specialized agents
agent-coordination:
  primary: product-owner
  secondary: 
    - laboratory # For creative product exploration
    - ux-expert # For user experience validation
    - technical-architect # For feasibility assessment
  validation: scrum-master
  approval: stakeholder-group
  market-analysis: market-research-specialist

sections:
  - id: executive-summary
    title: Executive Summary
    instruction: |
      VC-SYS Enhancement: Executive summary for stakeholder alignment.
      
      Provide a concise executive summary (2-3 paragraphs) that captures:
      1. Product vision and value proposition
      2. Target market and user base
      3. Key success metrics and business impact
      4. Resource requirements and timeline
      
      This summary should enable executives to understand the project without reading the full PRD.
    elicit: true
    evidence-required: true
    template: |
      **Product Vision:** {{product_vision}}
      **Target Market:** {{target_market}}
      **Expected Business Impact:** {{business_impact}}
      **Investment Required:** {{resource_estimate}}
      **Timeline:** {{project_timeline}}
      **Success Metrics:** {{key_metrics}}

  - id: goals-context
    title: Goals and Background Context
    instruction: |
      Ask if Project Brief document is available. If NO Project Brief exists, STRONGLY recommend creating one first using project-brief-tmpl (it provides essential foundation: problem statement, target users, success metrics, MVP scope, constraints). If user insists on PRD without brief, gather this information during Goals section. If Project Brief exists, review and use it to populate Goals (bullet list of desired outcomes) and Background Context (1-2 paragraphs on what this solves and why) so we can determine what is and is not in scope for PRD mvp. Either way this is critical to determine the requirements. Include Change Log table.
      
      VC-SYS Enhancement: Include market validation and competitive analysis references.
    evidence-required: true
    sections:
      - id: goals
        title: Goals
        type: bullet-list
        instruction: |
          Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires.
          
          VC-SYS Enhancement: Include measurable success criteria and business KPIs.
        template: "- {{goal}} - _Success Metric:_ {{metric}} - _Business Impact:_ {{impact}}"
        
      - id: background
        title: Background Context
        type: paragraphs
        instruction: |
          1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is.
          
          VC-SYS Enhancement: Include market research findings and competitive landscape analysis.
        
      - id: market-context
        title: Market Context
        instruction: |
          VC-SYS Enhancement: Market analysis and validation.
          
          Provide market context including:
          1. Market size and opportunity
          2. Key competitors and differentiation
          3. Market trends and timing
          4. Validation evidence (surveys, interviews, analytics)
        template: |
          **Market Opportunity:** {{market_size}}
          **Key Competitors:** {{competitors}}
          **Differentiation:** {{unique_value}}
          **Market Validation:** {{validation_evidence}}
          **Market Trends:** {{relevant_trends}}
        evidence-required: true
        
      - id: changelog
        title: Change Log
        type: table
        columns: [Date, Version, Description, Author, Stakeholder Sign-off]
        instruction: Track document versions, changes, and stakeholder approvals

  - id: user-personas
    title: User Personas and Journey Mapping
    instruction: |
      VC-SYS Enhancement: Detailed user personas with journey mapping.
      
      Define target user personas and their journeys:
      1. Primary and secondary user personas
      2. User needs and pain points
      3. Current user journeys and desired improvements
      4. User research and validation data
    elicit: true
    evidence-required: true
    sections:
      - id: primary-personas
        title: Primary User Personas
        repeatable: true
        template: |
          **Persona:** {{persona_name}}
          **Demographics:** {{demographics}}
          **Goals:** {{user_goals}}
          **Pain Points:** {{pain_points}}
          **Tech Savviness:** {{tech_level}}/10
          **Usage Context:** {{usage_context}}
          **Success Metrics:** {{persona_metrics}}
          
      - id: user-journeys
        title: User Journey Maps
        repeatable: true
        template: |
          **Journey:** {{journey_name}}
          **Persona:** {{target_persona}}
          **Trigger:** {{journey_trigger}}
          **Steps:** {{journey_steps}}
          **Pain Points:** {{journey_pain_points}}
          **Opportunities:** {{improvement_opportunities}}
          
      - id: user-research
        title: User Research Summary
        template: |
          **Research Methods:** {{research_methods}}
          **Sample Size:** {{sample_size}}
          **Key Findings:** {{key_findings}}
          **Validation Evidence:** {{validation_data}}
          **Research Confidence:** {{confidence_level}}/10

  - id: requirements
    title: Requirements
    instruction: |
      Draft the list of functional and non functional requirements under the two child sections.
      
      VC-SYS Enhancement: Include security, accessibility, performance, and compliance requirements.
    elicit: true
    evidence-required: true
    sections:
      - id: functional
        title: Functional Requirements
        type: numbered-list
        prefix: FR
        instruction: |
          Each Requirement will be a bullet markdown and an identifier sequence starting with FR.
          
          VC-SYS Enhancement: Include user story mapping and acceptance criteria alignment.
        examples:
          - "FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently."
          - "FR12: The system provides real-time collaboration features allowing multiple users to work on the same project simultaneously."
          - "FR18: Users can export their data in multiple formats (CSV, JSON, PDF) with custom filtering options."
          
      - id: non-functional
        title: Non-Functional Requirements
        type: numbered-list
        prefix: NFR
        instruction: |
          Each Requirement will be a bullet markdown and an identifier sequence starting with NFR.
          
          VC-SYS Enhancement: Include comprehensive performance, security, accessibility, and compliance requirements.
        examples:
          - "NFR1: AWS service usage must aim to stay within free-tier limits where feasible."
          - "NFR7: The system must achieve WCAG 2.1 AA compliance for accessibility."
          - "NFR12: API response times must not exceed 200ms for 95% of requests."
          - "NFR15: The application must support 1000 concurrent users with <2s page load times."
          - "NFR23: All sensitive data must be encrypted at rest using AES-256 encryption."
          
      - id: security-requirements
        title: Security Requirements
        instruction: |
          VC-SYS Enhancement: Dedicated security requirements section.
        type: numbered-list
        prefix: SR
        examples:
          - "SR1: Implement multi-factor authentication for all user accounts."
          - "SR5: All API endpoints must implement rate limiting and request validation."
          - "SR8: User session management must include automatic timeout after 30 minutes of inactivity."
          
      - id: compliance-requirements
        title: Compliance Requirements
        instruction: |
          VC-SYS Enhancement: Regulatory and compliance requirements.
        type: numbered-list
        prefix: CR
        examples:
          - "CR1: System must comply with GDPR data protection regulations."
          - "CR3: Audit trails must be maintained for all data modifications."
          - "CR7: Data retention policies must align with industry regulations."

  - id: ui-goals
    title: User Interface Design Goals
    condition: PRD has UX/UI requirements
    instruction: |
      Capture high-level UI/UX vision to guide Design Architect and to inform story creation. Steps:
      
      1. Pre-fill all subsections with educated guesses based on project context
      2. Present the complete rendered section to user
      3. Clearly let the user know where assumptions were made
      4. Ask targeted questions for unclear/missing elements or areas needing more specification
      5. This is NOT detailed UI spec - focus on product vision and user goals
      
      VC-SYS Enhancement: Include accessibility-first design and performance considerations.
    elicit: true
    evidence-required: true
    choices:
      accessibility: [None, WCAG AA, WCAG AAA, Custom Requirements]
      platforms: [Web Responsive, Mobile Only, Desktop Only, Cross-Platform, PWA]
      design_system: [Custom, Material Design, Ant Design, Chakra UI, Tailwind Components]
    sections:
      - id: ux-vision
        title: Overall UX Vision
        template: |
          **Design Philosophy:** {{design_philosophy}}
          **User Experience Goals:** {{ux_goals}}
          **Interaction Principles:** {{interaction_principles}}
          **Accessibility Priority:** {{accessibility_priority}}
          **Performance Targets:** {{ux_performance_targets}}
          
      - id: design-system
        title: Design System Requirements
        instruction: |
          VC-SYS Enhancement: Design system and component strategy.
        template: |
          **Design System Approach:** {{design_system_choice}}
          **Component Library:** {{component_strategy}}
          **Design Tokens:** {{token_approach}}
          **Theme Support:** {{theme_requirements}}
          **Consistency Standards:** {{consistency_rules}}
          
      - id: interaction-paradigms
        title: Key Interaction Paradigms
        template: |
          **Primary Interactions:** {{primary_interactions}}
          **Navigation Patterns:** {{navigation_approach}}
          **Feedback Mechanisms:** {{user_feedback}}
          **Error Handling:** {{error_ux}}
          **Loading States:** {{loading_strategy}}
          
      - id: core-screens
        title: Core Screens and Views
        instruction: |
          From a product perspective, what are the most critical screens or views necessary to deliver the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories.
          
          VC-SYS Enhancement: Include responsive behavior and accessibility considerations.
        examples:
          - "Login Screen - Multi-factor authentication with accessibility support"
          - "Main Dashboard - Real-time data with loading states and error handling"  
          - "Item Detail Page - CRUD operations with optimistic updates"
          - "Settings Page - User preferences with instant preview"
          - "Admin Panel - Role-based access with audit logging"
          
      - id: accessibility
        title: "Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}"
        template: |
          **Compliance Level:** {{accessibility_level}}
          **Screen Reader Support:** {{screen_reader_requirements}}
          **Keyboard Navigation:** {{keyboard_requirements}}
          **Color Contrast:** {{contrast_requirements}}
          **Focus Management:** {{focus_requirements}}
          **Testing Strategy:** {{accessibility_testing}}
          
      - id: performance-ux
        title: Performance and UX Requirements
        instruction: |
          VC-SYS Enhancement: Performance requirements from UX perspective.
        template: |
          **Page Load Targets:** {{load_time_targets}}
          **Interaction Responsiveness:** {{interaction_targets}}
          **Offline Capabilities:** {{offline_requirements}}
          **Progressive Enhancement:** {{progressive_strategy}}
          **Mobile Performance:** {{mobile_performance}}
          
      - id: branding
        title: Branding Requirements
        instruction: Any known branding elements or style guides that must be incorporated?
        examples:
          - "Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions."
          - "Attached is the full color palette and tokens for our corporate branding."
          - "Modern, minimalist design with accessibility-first approach and high contrast support."
          
      - id: target-platforms
        title: "Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform|PWA}"
        examples:
          - "Web Responsive with PWA capabilities for mobile users"
          - "iPhone and Android native apps with shared React Native codebase"
          - "Desktop-first web application with tablet support"
          - "Cross-platform PWA with offline-first architecture"

  - id: technical-assumptions
    title: Technical Assumptions
    instruction: |
      Gather technical decisions that will guide the Architect. Steps:
      
      1. Check if .bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
      2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
      3. For unknowns, offer guidance based on project goals and MVP scope
      4. Document ALL technical choices with rationale (why this choice fits the project)
      5. These become constraints for the Architect - be specific and complete
      
      VC-SYS Enhancement: Include security, performance, and scalability considerations.
    elicit: true
    evidence-required: true
    choices:
      repository: [Monorepo, Polyrepo, Multi-repo]
      architecture: [Monolith, Microservices, Serverless, Hybrid]
      testing: [Unit Only, Unit + Integration, Full Testing Pyramid, TDD]
      deployment: [Traditional, Containerized, Serverless, Hybrid]
      security: [Basic, Enhanced, Enterprise, Compliance-focused]
    sections:
      - id: repository-structure
        title: "Repository Structure: {Monorepo|Polyrepo|Multi-repo}"
        template: |
          **Structure:** {{repo_structure}}
          **Rationale:** {{repo_rationale}}
          **Tooling:** {{repo_tooling}}
          **Workflow Impact:** {{workflow_considerations}}
          
      - id: service-architecture
        title: Service Architecture
        instruction: |
          CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).
          
          VC-SYS Enhancement: Include scalability and performance considerations.
        template: |
          **Architecture Style:** {{architecture_choice}}
          **Scalability Strategy:** {{scaling_approach}}
          **Service Communication:** {{communication_patterns}}
          **Data Architecture:** {{data_strategy}}
          **Deployment Model:** {{deployment_approach}}
          
      - id: technology-stack
        title: Technology Stack Preferences
        instruction: |
          VC-SYS Enhancement: Comprehensive technology preferences.
        template: |
          **Frontend Framework:** {{frontend_choice}} - {{frontend_rationale}}
          **Backend Framework:** {{backend_choice}} - {{backend_rationale}}
          **Database:** {{database_choice}} - {{database_rationale}}
          **Authentication:** {{auth_choice}} - {{auth_rationale}}
          **Deployment Platform:** {{platform_choice}} - {{platform_rationale}}
          **CI/CD:** {{cicd_choice}} - {{cicd_rationale}}
          
      - id: performance-requirements
        title: Performance and Scalability Requirements
        instruction: |
          VC-SYS Enhancement: Performance and scalability technical requirements.
        template: |
          **Response Time Targets:** {{response_targets}}
          **Concurrent User Capacity:** {{user_capacity}}
          **Data Volume Expectations:** {{data_volume}}
          **Geographic Distribution:** {{geo_requirements}}
          **Caching Strategy:** {{caching_approach}}
          **Monitoring Requirements:** {{monitoring_needs}}
          
      - id: security-architecture
        title: Security Architecture Requirements
        instruction: |
          VC-SYS Enhancement: Security technical requirements.
        template: |
          **Authentication Method:** {{auth_method}}
          **Authorization Model:** {{authz_approach}}
          **Data Encryption:** {{encryption_requirements}}
          **API Security:** {{api_security}}
          **Compliance Needs:** {{compliance_requirements}}
          **Security Monitoring:** {{security_monitoring}}
          
      - id: testing-requirements
        title: Testing Requirements
        instruction: |
          CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).
          
          VC-SYS Enhancement: Include security and performance testing.
        template: |
          **Testing Strategy:** {{testing_approach}}
          **Coverage Targets:** {{coverage_requirements}}
          **Test Automation:** {{automation_level}}
          **Performance Testing:** {{performance_testing}}
          **Security Testing:** {{security_testing}}
          **Accessibility Testing:** {{accessibility_testing}}
          
      - id: additional-assumptions
        title: Additional Technical Assumptions and Requests
        instruction: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items

  - id: success-metrics
    title: Success Metrics and KPIs
    instruction: |
      VC-SYS Enhancement: Comprehensive success measurement framework.
      
      Define measurable success criteria:
      1. Business metrics (revenue, cost savings, efficiency gains)
      2. User metrics (engagement, satisfaction, retention)
      3. Technical metrics (performance, reliability, scalability)
      4. Product metrics (feature adoption, user journeys)
    elicit: true
    evidence-required: true
    sections:
      - id: business-metrics
        title: Business Success Metrics
        template: |
          **Revenue Impact:** {{revenue_metrics}}
          **Cost Savings:** {{cost_metrics}}
          **Efficiency Gains:** {{efficiency_metrics}}
          **Market Share:** {{market_metrics}}
          **ROI Targets:** {{roi_expectations}}
          
      - id: user-metrics
        title: User Success Metrics
        template: |
          **User Engagement:** {{engagement_metrics}}
          **User Satisfaction:** {{satisfaction_metrics}}
          **User Retention:** {{retention_metrics}}
          **Feature Adoption:** {{adoption_metrics}}
          **User Growth:** {{growth_metrics}}
          
      - id: technical-metrics
        title: Technical Success Metrics
        template: |
          **Performance Metrics:** {{performance_metrics}}
          **Reliability Metrics:** {{reliability_metrics}}
          **Scalability Metrics:** {{scalability_metrics}}
          **Security Metrics:** {{security_metrics}}
          **Quality Metrics:** {{quality_metrics}}
          
      - id: measurement-plan
        title: Measurement and Analytics Plan
        template: |
          **Analytics Tools:** {{analytics_stack}}
          **Monitoring Strategy:** {{monitoring_approach}}
          **Reporting Frequency:** {{reporting_schedule}}
          **Success Review Cadence:** {{review_schedule}}
          **Adjustment Triggers:** {{adjustment_criteria}}

  - id: risk-assessment
    title: Risk Assessment and Mitigation
    instruction: |
      VC-SYS Enhancement: Comprehensive risk analysis and mitigation planning.
      
      Identify and assess project risks:
      1. Technical risks (complexity, dependencies, scalability)
      2. Business risks (market changes, competition, resources)
      3. User risks (adoption, usability, satisfaction)
      4. Operational risks (security, compliance, maintenance)
    elicit: true
    evidence-required: true
    sections:
      - id: risk-matrix
        title: Risk Assessment Matrix
        type: table
        columns: [Risk, Category, Probability, Impact, Risk Score, Mitigation Strategy, Owner]
        template: "{{risk_matrix_rows}}"
        
      - id: technical-risks
        title: Technical Risks
        template: |
          **High Priority Technical Risks:**
          {{high_tech_risks}}
          
          **Medium Priority Technical Risks:**
          {{medium_tech_risks}}
          
          **Mitigation Strategies:**
          {{tech_risk_mitigation}}
          
      - id: business-risks
        title: Business and Market Risks
        template: |
          **Market Risks:** {{market_risks}}
          **Competitive Risks:** {{competitive_risks}}
          **Resource Risks:** {{resource_risks}}
          **Timeline Risks:** {{timeline_risks}}
          **Mitigation Plans:** {{business_risk_mitigation}}
          
      - id: contingency-planning
        title: Contingency Planning
        template: |
          **Scenario Planning:** {{scenarios}}
          **Fallback Options:** {{fallback_plans}}
          **Success Criteria Adjustments:** {{criteria_adjustments}}
          **Go/No-Go Decision Points:** {{decision_gates}}

  - id: epic-list
    title: Epic List
    instruction: |
      Present a high-level list of all epics for user approval. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
      
      CRITICAL: Epics MUST be logically sequential following agile best practices:
      
      - Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
      - Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page - remember this when we produce the stories for the first epic!
      - Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
      - Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
      - Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
      - Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.
      
      VC-SYS Enhancement: Include value delivery timeline and dependency mapping.
    elicit: true
    evidence-required: true
    template: |
      **Epic Priority and Sequencing Rationale:**
      {{epic_sequencing_rationale}}
      
      **Value Delivery Timeline:**
      {{value_timeline}}
      
      **Dependencies Between Epics:**
      {{epic_dependencies}}
      
    examples:
      - "Epic 1: Foundation & Authentication Infrastructure: Establish project setup, CI/CD pipeline, and secure user authentication with basic user management"
      - "Epic 2: Core Business Entity Management: Create and manage primary domain objects with full CRUD operations and data validation"
      - "Epic 3: Advanced User Workflows & Collaboration: Enable key user journeys, real-time features, and multi-user collaboration"
      - "Epic 4: Analytics, Reporting & Performance Optimization: Provide comprehensive insights, reporting capabilities, and performance monitoring"

  - id: epic-details
    title: Epic {{epic_number}} {{epic_title}}
    repeatable: true
    instruction: |
      After the epic list is approved, present each epic with all its stories and acceptance criteria as a complete review unit.
      
      For each epic provide expanded goal (2-3 sentences describing the objective and value all the stories will achieve).
      
      CRITICAL STORY SEQUENCING REQUIREMENTS:
      
      - Stories within each epic MUST be logically sequential
      - Each story should be a "vertical slice" delivering complete functionality aside from early enabler stories for project foundation
      - No story should depend on work from a later story or epic
      - Identify and note any direct prerequisite stories
      - Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
      - Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
      - Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
      - Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
      - If a story seems complex, break it down further as long as it can deliver a vertical slice
      
      VC-SYS Enhancement: Include story priority, effort estimation, and dependency tracking.
    elicit: true
    evidence-required: true
    template: |
      **Epic Goal:** {{epic_goal}}
      
      **Business Value:** {{epic_business_value}}
      **User Impact:** {{epic_user_impact}}
      **Technical Foundation:** {{epic_technical_impact}}
      **Success Criteria:** {{epic_success_criteria}}
      **Estimated Timeline:** {{epic_timeline}}
    sections:
      - id: story
        title: Story {{epic_number}}.{{story_number}} {{story_title}}
        repeatable: true
        template: |
          **Priority:** {{story_priority}} | **Effort:** {{story_effort}} | **Risk:** {{story_risk}}
          
          As a {{user_type}},
          I want {{action}},
          so that {{benefit}}.
          
          **Business Value:** {{story_business_value}}
          **User Impact:** {{story_user_impact}}
          **Dependencies:** {{story_dependencies}}
        sections:
          - id: acceptance-criteria
            title: Acceptance Criteria
            type: numbered-list
            item_template: "AC{{criterion_number}}: {{criteria}}"
            repeatable: true
            instruction: |
              Define clear, comprehensive, and testable acceptance criteria that:
              
              - Precisely define what "done" means from a functional perspective
              - Are unambiguous and serve as basis for verification
              - Include any critical non-functional requirements from the PRD
              - Consider local testability for backend/data components
              - Specify UI/UX requirements and framework adherence where applicable
              - Include accessibility requirements where applicable
              - Include performance requirements where applicable
              - Include security requirements where applicable
              - Avoid cross-cutting concerns that should be in other stories or PRD sections
              
          - id: technical-notes
            title: Technical Considerations
            instruction: |
              VC-SYS Enhancement: Technical guidance for implementation.
            template: |
              **Implementation Complexity:** {{implementation_complexity}}/10
              **Technology Dependencies:** {{tech_dependencies}}
              **Performance Considerations:** {{performance_notes}}
              **Security Considerations:** {{security_notes}}
              **Accessibility Requirements:** {{accessibility_notes}}
              **Testing Requirements:** {{testing_notes}}

  - id: checklist-results
    title: Checklist Results Report
    instruction: |
      Before running the checklist and drafting the prompts, offer to output the full updated PRD. If outputting it, confirm with the user that you will be proceeding to run the checklist and produce the report. Once the user confirms, execute the pm-checklist and populate the results in this section.
      
      VC-SYS Enhancement: Include stakeholder sign-off tracking and validation metrics.
    sections:
      - id: validation-summary
        title: Validation Summary
        template: |
          **Completeness Score:** {{completeness_score}}/10
          **Clarity Score:** {{clarity_score}}/10
          **Feasibility Score:** {{feasibility_score}}/10
          **Stakeholder Alignment:** {{alignment_score}}/10
          **Risk Assessment:** {{risk_score}}/10
          
      - id: stakeholder-signoff
        title: Stakeholder Sign-off
        type: table
        columns: [Stakeholder, Role, Sign-off Status, Comments, Date]
        template: "{{signoff_table}}"

  - id: next-steps
    title: Next Steps
    sections:
      - id: implementation-roadmap
        title: Implementation Roadmap
        instruction: |
          VC-SYS Enhancement: Detailed implementation planning.
        template: |
          **Phase 1:** {{phase_1_description}} ({{phase_1_timeline}})
          **Phase 2:** {{phase_2_description}} ({{phase_2_timeline}})
          **Phase 3:** {{phase_3_description}} ({{phase_3_timeline}})
          
          **Key Milestones:** {{key_milestones}}
          **Resource Requirements:** {{resource_needs}}
          **Success Gates:** {{success_checkpoints}}
          
      - id: ux-expert-prompt
        title: UX Expert Prompt
        instruction: |
          This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input.
          
          VC-SYS Enhancement: Include accessibility and performance requirements.
        template: |
          "Please create a comprehensive UX/UI architecture for {{project_name}} based on this PRD. Focus on:
          - {{accessibility_level}} accessibility compliance
          - {{performance_targets}} performance requirements  
          - {{design_system_approach}} design system implementation
          - User personas: {{key_personas}}
          - Core user journeys: {{critical_journeys}}
          Reference the UI Design Goals section for detailed requirements."
          
      - id: architect-prompt
        title: Architect Prompt
        instruction: |
          This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.
          
          VC-SYS Enhancement: Include security, performance, and scalability requirements.
        template: |
          "Please create a comprehensive technical architecture for {{project_name}} based on this PRD. Key requirements:
          - {{architecture_style}} architecture with {{scalability_requirements}}
          - {{tech_stack_summary}} technology stack
          - {{security_requirements}} security implementation
          - {{performance_requirements}} performance targets
          - {{testing_strategy}} testing approach
          Reference the Technical Assumptions and Requirements sections for detailed specifications."