template:
  id: brownfield-architecture-template-v3-enhanced
  name: VC-SYS Enhanced Brownfield Architecture
  version: 3.0
  output:
    format: markdown
    filename: docs/brownfield-architecture.md
    title: "{{project_name}} Brownfield Enhancement Architecture"

# VC-SYS Enhancement: Agent permissions and evidence requirements
permissions:
  owner: integration-specialist
  editors: [technical-architect, developer, qa, devops]
  viewers: [scrum-master, product-owner, ux-expert]
  evidence-required: true
  anti-hallucination: enabled
  legacy-analysis: required
  risk-assessment: mandatory

workflow:
  mode: interactive
  elicitation: advanced-elicitation
  facilitation: laboratory-agent
  validation: architect-checklist
  risk-monitoring: continuous
  
# VC-SYS Enhancement: Integration with specialized agents
agent-coordination:
  primary: integration-specialist # Specialist in legacy system integration
  secondary: 
    - technical-architect # For overall architecture guidance
    - laboratory # For creative solutions to legacy constraints
    - qa # For regression testing strategy
  validation: qa
  approval: product-owner
  risk-assessor: security

sections:
  - id: introduction
    title: Introduction
    instruction: |
      IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
      
      This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
      
      1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
      
      2. **REQUIRED INPUTS**:
         - Completed brownfield-prd.md
         - Existing project technical documentation (from docs folder or user-provided)
         - Access to existing project structure (IDE or uploaded files)
         - Performance baselines from existing system
         - Security audit reports if available
         - Known issues and technical debt documentation
      
      3. **DEEP ANALYSIS MANDATE**: You MUST conduct thorough analysis of the existing codebase, architecture patterns, and technical constraints before making ANY architectural recommendations. Every suggestion must be based on actual project analysis, not assumptions.
      
      4. **CONTINUOUS VALIDATION**: Throughout this process, explicitly validate your understanding with the user. For every architectural decision, confirm: "Based on my analysis of your existing system, I recommend [decision] because [evidence from actual project]. Does this align with your system's reality?"
      
      5. **VC-SYS RISK ASSESSMENT**: All brownfield enhancements require risk scoring and mitigation planning. Use the integration-specialist agent for detailed risk analysis.
      
      If any required inputs are missing, request them before proceeding.
    elicit: true
    evidence-required: true
    sections:
      - id: intro-content
        content: |
          This document outlines the architectural approach for enhancing {{project_name}} with {{enhancement_description}}. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development of new features while ensuring seamless integration with the existing system, minimizing risk, and preserving system stability.
          
          **Relationship to Existing Architecture:**
          This document supplements existing project architecture by defining how new components will integrate with current systems. Where conflicts arise between new and existing patterns, this document provides guidance on maintaining consistency while implementing enhancements.
          
          **VC-SYS Enhancements:**
          - Risk-based integration planning with measurable criteria
          - Anti-corruption layer design for clean boundaries
          - Strangler fig pattern support for progressive migration
          - Evidence-based decision making with legacy system constraints
          - Comprehensive regression testing strategy
          
      - id: existing-project-analysis
        title: Existing Project Analysis
        instruction: |
          Analyze the existing project structure and architecture:
          
          1. Review existing documentation in docs folder
          2. Examine current technology stack and versions
          3. Identify existing architectural patterns and conventions
          4. Note current deployment and infrastructure setup
          5. Document any constraints or limitations
          6. Analyze performance baselines and bottlenecks
          7. Identify security vulnerabilities and compliance gaps
          8. Map technical debt and areas of concern
          
          CRITICAL: After your analysis, explicitly validate your findings: "Based on my analysis of your project, I've identified the following about your existing system: [key findings]. Please confirm these observations are accurate before I proceed with architectural recommendations."
          
          VC-SYS Enhancement: Use evidence-based analysis tools to verify findings.
        elicit: true
        evidence-required: true
        sections:
          - id: current-state
            title: Current Project State
            template: |
              - **Primary Purpose:** {{existing_project_purpose}}
              - **Current Tech Stack:** {{existing_tech_summary}}
              - **Architecture Style:** {{existing_architecture_style}}
              - **Deployment Method:** {{existing_deployment_approach}}
              - **Performance Baseline:** {{performance_metrics}}
              - **Security Posture:** {{security_assessment}}
              - **Technical Debt Score:** {{debt_score}}/10
              
          - id: legacy-system-assessment
            title: Legacy System Assessment
            template: |
              **System Age:** {{system_age}}
              **Modernization Readiness:** {{modernization_score}}/10
              **Integration Complexity:** {{complexity_score}}/10
              **Risk Level:** {{risk_level}}
              
              **Key Challenges:**
              - {{challenge_1}}
              - {{challenge_2}}
              - {{challenge_3}}
              
              **Opportunities:**
              - {{opportunity_1}}
              - {{opportunity_2}}
              
          - id: available-docs
            title: Available Documentation
            type: bullet-list
            template: "- {{existing_docs_summary}} - _Quality:_ {{doc_quality}}/10"
            
          - id: constraints
            title: Identified Constraints
            type: table
            columns: [Constraint, Impact, Mitigation, Risk]
            template: "{{constraints_table}}"
            
      - id: changelog
        title: Change Log
        type: table
        columns: [Change, Date, Version, Description, Author, Risk Assessment]
        instruction: Track document versions, changes, and associated risks

  - id: risk-assessment
    title: Risk Assessment and Mitigation
    instruction: |
      VC-SYS Enhancement: Comprehensive risk assessment for brownfield integration.
      
      Conduct thorough risk analysis:
      1. Technical risks (compatibility, performance, stability)
      2. Business risks (downtime, data loss, user impact)
      3. Security risks (new vulnerabilities, compliance)
      4. Operational risks (deployment, rollback, monitoring)
      5. Timeline risks (complexity underestimation)
    elicit: true
    evidence-required: true
    sections:
      - id: risk-matrix
        title: Risk Matrix
        type: table
        columns: [Risk, Probability, Impact, Score, Mitigation, Owner]
        template: "{{risk_matrix}}"
        
      - id: risk-mitigation-plan
        title: Risk Mitigation Plan
        template: |
          **High Priority Mitigations:**
          {{high_priority_mitigations}}
          
          **Contingency Plans:**
          {{contingency_plans}}
          
          **Success Criteria:**
          {{success_criteria}}
          
          **Go/No-Go Decision Points:**
          {{decision_points}}

  - id: enhancement-scope
    title: Enhancement Scope and Integration Strategy
    instruction: |
      Define how the enhancement will integrate with the existing system:
      
      1. Review the brownfield PRD enhancement scope
      2. Identify integration points with existing code
      3. Define boundaries between new and existing functionality
      4. Establish compatibility requirements
      5. Design anti-corruption layers where needed
      6. Plan for progressive migration if applicable
      
      VALIDATION CHECKPOINT: Before presenting the integration strategy, confirm: "Based on my analysis, the integration approach I'm proposing takes into account [specific existing system characteristics]. These integration points and boundaries respect your current architecture patterns. Is this assessment accurate?"
      
      VC-SYS Enhancement: Use integration patterns library for proven approaches.
    elicit: true
    evidence-required: true
    sections:
      - id: enhancement-overview
        title: Enhancement Overview
        template: |
          **Enhancement Type:** {{enhancement_type}}
          **Scope:** {{enhancement_scope}}
          **Integration Impact:** {{integration_impact_level}}
          **Migration Strategy:** {{migration_approach}}
          **Timeline:** {{timeline_estimate}}
          
      - id: integration-patterns
        title: Integration Patterns
        template: |
          **Primary Pattern:** {{primary_pattern}}
          **Supporting Patterns:**
          - Anti-Corruption Layer: {{acl_usage}}
          - Strangler Fig: {{strangler_usage}}
          - Adapter Pattern: {{adapter_usage}}
          - Facade Pattern: {{facade_usage}}
          
      - id: integration-approach
        title: Integration Approach
        template: |
          **Code Integration Strategy:** {{code_integration_approach}}
          **Database Integration:** {{database_integration_approach}}
          **API Integration:** {{api_integration_approach}}
          **UI Integration:** {{ui_integration_approach}}
          **Event Integration:** {{event_integration_approach}}
          
      - id: anti-corruption-layer
        title: Anti-Corruption Layer Design
        condition: ACL pattern is being used
        template: |
          **Purpose:** {{acl_purpose}}
          **Boundary Definition:** {{boundary_definition}}
          **Translation Logic:** {{translation_approach}}
          **Validation Rules:** {{validation_rules}}
          **Performance Impact:** {{acl_performance}}
          
      - id: compatibility-requirements
        title: Compatibility Requirements
        template: |
          - **Existing API Compatibility:** {{api_compatibility}}
          - **Database Schema Compatibility:** {{db_compatibility}}
          - **UI/UX Consistency:** {{ui_compatibility}}
          - **Performance Impact:** {{performance_constraints}}
          - **Security Compliance:** {{security_compatibility}}
          - **Data Format Compatibility:** {{data_compatibility}}

  - id: migration-architecture
    title: Migration Architecture
    instruction: |
      VC-SYS Enhancement: Design progressive migration strategy.
      
      For significant enhancements requiring migration:
      1. Define migration phases
      2. Design rollback procedures
      3. Plan data migration
      4. Establish success criteria
      5. Create monitoring strategy
    elicit: true
    condition: Enhancement requires migration
    sections:
      - id: migration-strategy
        title: Migration Strategy
        template: |
          **Migration Type:** {{migration_type}}
          **Phasing Approach:** {{phasing_approach}}
          **Rollback Window:** {{rollback_window}}
          **Data Migration:** {{data_migration_approach}}
          
      - id: migration-phases
        title: Migration Phases
        type: table
        columns: [Phase, Description, Duration, Success Criteria, Rollback Plan]
        template: "{{migration_phases_table}}"
        
      - id: strangler-fig-implementation
        title: Strangler Fig Implementation
        condition: Using strangler fig pattern
        template: |
          **Target Components:** {{target_components}}
          **Routing Strategy:** {{routing_strategy}}
          **Feature Flags:** {{feature_flag_approach}}
          **Monitoring:** {{monitoring_approach}}
          **Completion Criteria:** {{completion_criteria}}

  - id: tech-stack-alignment
    title: Tech Stack Alignment
    instruction: |
      Ensure new components align with existing technology choices:
      
      1. Use existing technology stack as the foundation
      2. Only introduce new technologies if absolutely necessary
      3. Justify any new additions with clear rationale and evidence
      4. Ensure version compatibility with existing dependencies
      5. Plan for dependency conflicts resolution
      
      VC-SYS Enhancement: Include total cost of ownership for new technologies.
    elicit: true
    evidence-required: true
    sections:
      - id: existing-stack
        title: Existing Technology Stack
        type: table
        columns: [Category, Current Technology, Version, Usage in Enhancement, Compatibility, Notes]
        instruction: Document the current stack that must be maintained or integrated with
        
      - id: dependency-analysis
        title: Dependency Analysis
        template: |
          **Dependency Conflicts:** {{conflicts_identified}}
          **Resolution Strategy:** {{resolution_approach}}
          **Version Constraints:** {{version_constraints}}
          **Update Requirements:** {{update_requirements}}
          
      - id: new-tech-additions
        title: New Technology Additions
        condition: Enhancement requires new technologies
        type: table
        columns: [Technology, Version, Purpose, Rationale, Integration Method, TCO Impact]
        instruction: Only include if new technologies are required for the enhancement

  - id: data-architecture
    title: Data Architecture and Migration
    instruction: |
      VC-SYS Enhancement: Comprehensive data architecture with migration planning.
      
      Define new data models and migration strategy:
      
      1. Identify new entities required for the enhancement
      2. Define relationships with existing data models
      3. Plan database schema changes (additions, modifications)
      4. Design data migration procedures
      5. Ensure backward compatibility
      6. Plan for data integrity validation
    elicit: true
    evidence-required: true
    sections:
      - id: new-models
        title: New Data Models
        repeatable: true
        sections:
          - id: model
            title: "{{model_name}}"
            template: |
              **Purpose:** {{model_purpose}}
              **Integration:** {{integration_with_existing}}
              **Data Volume:** {{expected_volume}}
              **Growth Rate:** {{growth_projection}}
              
              **Key Attributes:**
              - {{attribute_1}}: {{type_1}} - {{description_1}} - {{validation_1}}
              - {{attribute_2}}: {{type_2}} - {{description_2}} - {{validation_2}}
              
              **Relationships:**
              - **With Existing:** {{existing_relationships}}
              - **With New:** {{new_relationships}}
              
              **Migration Requirements:**
              - **Source Data:** {{source_data}}
              - **Transformation:** {{transformation_logic}}
              - **Validation:** {{validation_approach}}
              
      - id: schema-integration
        title: Schema Integration Strategy
        template: |
          **Database Changes Required:**
          - **New Tables:** {{new_tables_list}}
          - **Modified Tables:** {{modified_tables_list}}
          - **New Indexes:** {{new_indexes_list}}
          - **Constraints:** {{new_constraints}}
          
          **Migration Strategy:**
          - **Approach:** {{migration_approach}}
          - **Downtime:** {{expected_downtime}}
          - **Rollback:** {{rollback_procedure}}
          - **Validation:** {{validation_steps}}
          
          **Backward Compatibility:**
          - {{compatibility_measure_1}}
          - {{compatibility_measure_2}}
          
      - id: data-migration-plan
        title: Data Migration Plan
        template: |
          **Migration Phases:**
          1. {{phase_1}} - {{phase_1_validation}}
          2. {{phase_2}} - {{phase_2_validation}}
          3. {{phase_3}} - {{phase_3_validation}}
          
          **Data Integrity Checks:**
          - Pre-migration: {{pre_migration_checks}}
          - During migration: {{during_migration_checks}}
          - Post-migration: {{post_migration_checks}}
          
          **Performance Impact:**
          - Expected duration: {{migration_duration}}
          - Resource usage: {{resource_impact}}
          - User impact: {{user_impact}}

  - id: component-architecture
    title: Component Architecture
    instruction: |
      Define new components and their integration with existing architecture:
      
      1. Identify new components required for the enhancement
      2. Define interfaces with existing components
      3. Establish clear boundaries and responsibilities
      4. Plan integration points and data flow
      5. Design adapter layers where needed
      
      MANDATORY VALIDATION: Before presenting component architecture, confirm: "The new components I'm proposing follow the existing architectural patterns I identified in your codebase: [specific patterns]. The integration interfaces respect your current component structure and communication patterns. Does this match your project's reality?"
      
      VC-SYS Enhancement: Use component compatibility scoring.
    elicit: true
    evidence-required: true
    sections:
      - id: new-components
        title: New Components
        repeatable: true
        sections:
          - id: component
            title: "{{component_name}}"
            template: |
              **Responsibility:** {{component_description}}
              **Integration Points:** {{integration_points}}
              **Compatibility Score:** {{compatibility_score}}/10
              
              **Key Interfaces:**
              - {{interface_1}} - {{interface_1_purpose}}
              - {{interface_2}} - {{interface_2_purpose}}
              
              **Dependencies:**
              - **Existing Components:** {{existing_dependencies}}
              - **New Components:** {{new_dependencies}}
              - **External Libraries:** {{external_dependencies}}
              
              **Technology Stack:** {{component_tech_details}}
              
              **Adapter Requirements:**
              - {{adapter_1}} - {{adapter_1_purpose}}
              
      - id: interaction-diagram
        title: Component Interaction Diagram
        type: mermaid
        mermaid_type: graph
        instruction: Create Mermaid diagram showing how new components interact with existing ones, including adapters and ACL
        
      - id: integration-sequence
        title: Integration Sequence
        type: mermaid
        mermaid_type: sequence
        instruction: Show the sequence of interactions between new and existing components

  - id: api-integration
    title: API Design and Integration
    condition: Enhancement requires API changes
    instruction: |
      VC-SYS Enhancement: API integration with versioning and compatibility.
      
      Define new API endpoints and integration with existing APIs:
      
      1. Plan new API endpoints required for the enhancement
      2. Ensure consistency with existing API patterns
      3. Define authentication and authorization integration
      4. Plan versioning strategy
      5. Design backward compatibility approach
      6. Create deprecation plan for replaced endpoints
    elicit: true
    evidence-required: true
    sections:
      - id: api-strategy
        title: API Integration Strategy
        template: |
          **API Integration Strategy:** {{api_integration_strategy}}
          **Authentication:** {{auth_integration}}
          **Versioning:** {{versioning_approach}}
          **Backward Compatibility:** {{backward_compat_approach}}
          **Deprecation Timeline:** {{deprecation_timeline}}
          
      - id: api-versioning
        title: API Versioning Plan
        template: |
          **Version Strategy:** {{version_strategy}}
          **Current Version:** {{current_version}}
          **New Version:** {{new_version}}
          **Compatibility Window:** {{compat_window}}
          **Migration Path:** {{migration_path}}
          
      - id: new-endpoints
        title: New API Endpoints
        repeatable: true
        sections:
          - id: endpoint
            title: "{{endpoint_name}}"
            template: |
              - **Method:** {{http_method}}
              - **Endpoint:** {{endpoint_path}}
              - **Version:** {{endpoint_version}}
              - **Purpose:** {{endpoint_purpose}}
              - **Integration:** {{integration_with_existing}}
              - **Authentication:** {{auth_required}}
              - **Rate Limiting:** {{rate_limit}}
            sections:
              - id: request
                title: Request
                type: code
                language: json
                template: "{{request_schema}}"
              - id: response
                title: Response
                type: code
                language: json
                template: "{{response_schema}}"
              - id: compatibility
                title: Backward Compatibility
                template: |
                  **Compatible with:** {{compatible_versions}}
                  **Breaking Changes:** {{breaking_changes}}
                  **Migration Guide:** {{migration_guide}}

  - id: testing-strategy
    title: Comprehensive Testing Strategy
    instruction: |
      VC-SYS Enhancement: Enhanced testing with regression focus.
      
      Define testing approach for the enhancement:
      
      1. Integrate with existing test suite
      2. Ensure existing functionality remains intact
      3. Plan for testing new features
      4. Define integration testing approach
      5. Create regression test suite
      6. Plan performance testing
      7. Design security testing
    elicit: true
    evidence-required: true
    sections:
      - id: test-coverage-analysis
        title: Test Coverage Analysis
        template: |
          **Current Coverage:** {{current_coverage}}%
          **Target Coverage:** {{target_coverage}}%
          **Critical Paths:** {{critical_paths}}
          **Risk Areas:** {{risk_areas}}
          
      - id: regression-testing
        title: Regression Testing Strategy
        template: |
          **Regression Suite Size:** {{regression_size}}
          **Automation Level:** {{automation_percentage}}%
          **Execution Frequency:** {{execution_frequency}}
          **Critical Scenarios:** {{critical_scenarios}}
          
          **Test Categories:**
          - Smoke Tests: {{smoke_tests}}
          - Functional Tests: {{functional_tests}}
          - Integration Tests: {{integration_tests}}
          - Performance Tests: {{performance_tests}}
          
      - id: test-environments
        title: Test Environment Strategy
        template: |
          **Environment Isolation:** {{isolation_approach}}
          **Data Management:** {{test_data_approach}}
          **Environment Parity:** {{parity_level}}
          **Refresh Strategy:** {{refresh_strategy}}
          
      - id: performance-testing
        title: Performance Testing
        template: |
          **Baseline Metrics:** {{baseline_metrics}}
          **Performance Targets:** {{performance_targets}}
          **Load Testing:** {{load_test_approach}}
          **Stress Testing:** {{stress_test_approach}}
          **Monitoring:** {{performance_monitoring}}

  - id: deployment-strategy
    title: Deployment and Rollout Strategy
    instruction: |
      VC-SYS Enhancement: Progressive deployment with monitoring.
      
      Define deployment strategy:
      1. Phased rollout approach
      2. Feature flag management
      3. Canary deployments
      4. Blue-green deployments
      5. Rollback procedures
      6. Monitoring and alerting
    elicit: true
    evidence-required: true
    sections:
      - id: deployment-phases
        title: Deployment Phases
        type: table
        columns: [Phase, Description, Target Users, Duration, Success Criteria, Rollback Trigger]
        template: "{{deployment_phases_table}}"
        
      - id: feature-flags
        title: Feature Flag Strategy
        template: |
          **Flag Management System:** {{flag_system}}
          **Flag Categories:** {{flag_categories}}
          **Activation Strategy:** {{activation_strategy}}
          **Emergency Kill Switches:** {{kill_switches}}
          
      - id: monitoring-strategy
        title: Monitoring and Alerting
        template: |
          **Key Metrics:**
          - Performance: {{performance_metrics}}
          - Error Rates: {{error_metrics}}
          - Business Metrics: {{business_metrics}}
          
          **Alert Thresholds:**
          - Critical: {{critical_thresholds}}
          - Warning: {{warning_thresholds}}
          
          **Response Procedures:**
          - Automated: {{automated_response}}
          - Manual: {{manual_response}}

  - id: operational-readiness
    title: Operational Readiness
    instruction: |
      VC-SYS Enhancement: Ensure operational excellence.
      
      Define operational requirements:
      1. Runbooks and playbooks
      2. Monitoring dashboards
      3. Support procedures
      4. Training requirements
      5. Documentation updates
    elicit: true
    sections:
      - id: runbooks
        title: Operational Runbooks
        template: |
          **Standard Operations:**
          - {{operation_1}} - {{procedure_1}}
          - {{operation_2}} - {{procedure_2}}
          
          **Emergency Procedures:**
          - {{emergency_1}} - {{response_1}}
          - {{emergency_2}} - {{response_2}}
          
      - id: support-readiness
        title: Support Readiness
        template: |
          **Training Requirements:** {{training_needs}}
          **Documentation Updates:** {{doc_updates}}
          **Support Tier Preparation:** {{support_preparation}}
          **Escalation Paths:** {{escalation_paths}}

  - id: success-criteria
    title: Success Criteria and Metrics
    instruction: |
      VC-SYS Enhancement: Define measurable success criteria.
      
      Establish clear success metrics:
      1. Technical success criteria
      2. Business success criteria
      3. User satisfaction metrics
      4. Operational metrics
    elicit: true
    evidence-required: true
    sections:
      - id: success-metrics
        title: Success Metrics
        type: table
        columns: [Metric, Current Value, Target Value, Measurement Method, Timeline]
        template: "{{success_metrics_table}}"
        
      - id: acceptance-criteria
        title: Acceptance Criteria
        template: |
          **Functional Acceptance:**
          {{functional_criteria}}
          
          **Performance Acceptance:**
          {{performance_criteria}}
          
          **Security Acceptance:**
          {{security_criteria}}
          
          **User Acceptance:**
          {{user_criteria}}

  - id: checklist-results
    title: Checklist Results Report
    instruction: |
      Execute the architect-checklist and populate results here, focusing on brownfield-specific validation.
      
      VC-SYS Enhancement: Include risk assessment validation and integration readiness score.
    sections:
      - id: validation-summary
        title: Validation Summary
        template: |
          **Integration Readiness:** {{integration_score}}/10
          **Risk Assessment Complete:** {{risk_complete}}
          **Regression Coverage:** {{regression_coverage}}%
          **Rollback Procedures:** {{rollback_ready}}
          **Monitoring Ready:** {{monitoring_ready}}

  - id: next-steps
    title: Next Steps
    instruction: |
      After completing the brownfield architecture:
      
      1. Review integration points with existing system
      2. Validate risk assessment with stakeholders
      3. Begin story implementation with Dev agent
      4. Set up deployment pipeline integration
      5. Plan rollback and monitoring procedures
      6. Schedule operational readiness review
    sections:
      - id: implementation-roadmap
        title: Implementation Roadmap
        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}}
          
          **Risk Review Points:**
          {{risk_review_schedule}}
          
      - id: story-manager-handoff
        title: Story Manager Handoff
        instruction: |
          Create a brief prompt for Story Manager to work with this brownfield enhancement. Include:
          - Reference to this architecture document
          - Key integration requirements validated with user
          - Existing system constraints based on actual project analysis
          - First story to implement with clear integration checkpoints
          - Risk mitigation requirements
          - Regression testing requirements
          - Emphasis on maintaining existing system integrity throughout implementation
          
      - id: developer-handoff
        title: Developer Handoff
        instruction: |
          Create a brief prompt for developers starting implementation. Include:
          - Reference to this architecture and existing coding standards analyzed from actual project
          - Integration requirements with existing codebase validated with user
          - Key technical decisions based on real project constraints
          - Existing system compatibility requirements with specific verification steps
          - Anti-corruption layer implementation guidelines
          - Clear sequencing of implementation to minimize risk to existing functionality
          - Regression testing requirements for each change
          - Performance baseline maintenance requirements