sf-agent-framework

# Release Validator Utility - Agent Instructions ## Purpose This utility provides instructions for AI agents to generate comprehensive release validation solutions for Salesforce deployments, ensuring releases meet quality, compliance, and business requirements before production deployment. ## Agent Instructions ### When to Generate Release Validation Generate release validation components when: - Releases need pre-deployment validation - Compliance requirements must be verified - Business sign-offs are required - Technical readiness needs confirmation - Risk assessment is necessary - Rollback plans need validation - Go/no-go decisions require automation ### Core Components to Generate #### 1. Release Validation Framework Generate validation components that: - Verify release package completeness - Validate deployment dependencies - Check environment readiness - Confirm testing completion - Verify documentation requirements - Assess deployment risks Key validation areas: - Technical validation - Business validation - Compliance validation - Security validation - Performance validation - Documentation validation #### 2. Release Checklist Engine Create checklists for: - Pre-release requirements - Deployment prerequisites - Testing completion - Approval workflows - Communication plans - Rollback procedures #### 3. Risk Assessment Module Implement risk evaluation for: - Technical complexity - Business impact - Data migration risks - Integration dependencies - Performance implications - Security considerations ### Configuration Requirements #### Custom Objects ```yaml Release_Definition__c: - Name (Text) - Release_Date__c (Date) - Environment__c (Picklist) - Status__c (Picklist) - Risk_Level__c (Picklist) - Business_Owner__c (Lookup) - Technical_Owner__c (Lookup) Release_Validation__c: - Release_Definition__c (Master-Detail) - Validation_Type__c (Picklist) - Status__c (Picklist) - Validator__c (Lookup) - Validation_Date__c (DateTime) - Comments__c (Long Text Area) - Is_Blocking__c (Checkbox) Release_Component__c: - Release_Definition__c (Master-Detail) - Component_Type__c (Picklist) - Component_Name__c (Text) - Version__c (Text) - Dependencies__c (Text Area) - Test_Coverage__c (Number) - Risk_Score__c (Number) ``` ### Validation Criteria to Implement #### Technical Validation ``` 1. Code coverage ≥ 80% 2. All tests passing 3. No critical bugs 4. Performance benchmarks met 5. Security scan passed 6. Integration tests completed ``` #### Business Validation ``` 1. UAT sign-off received 2. Training completed 3. Documentation approved 4. Communication sent 5. Business processes verified 6. Data migration validated ``` #### Compliance Validation ``` 1. Regulatory requirements met 2. Security policies followed 3. Data privacy compliance 4. Audit trail complete 5. Change management followed 6. Approval chain complete ``` ### Implementation Patterns #### Progressive Validation Pattern 1. Start early validations 2. Gate-based progression 3. Parallel validation tracks 4. Dependency management 5. Incremental approval 6. Final go/no-go decision #### Risk-Based Validation Pattern 1. Assess release complexity 2. Determine validation depth 3. Apply appropriate checks 4. Focus on high-risk areas 5. Streamline low-risk items 6. Optimize validation time #### Automated Decision Pattern 1. Collect all validations 2. Apply decision matrix 3. Calculate readiness score 4. Generate recommendations 5. Trigger notifications 6. Document decision ### Release Types and Validation #### Major Release Full validation including: - Complete regression testing - Performance testing - Security assessment - Business process validation - Training verification - Full documentation #### Minor Release Focused validation on: - Feature-specific testing - Targeted regression - Impacted area validation - Quick security scan - Update documentation #### Hotfix Release Expedited validation: - Critical fix testing - Smoke testing - Emergency approval - Minimal regression - Quick deployment ### Risk Assessment Matrix #### Risk Scoring ``` Risk Score = (Technical Complexity × Impact) + (Data Risk × 2) + (Integration Risk × 1.5) + (User Impact × 2) Where each factor is rated 1-5 ``` #### Risk Categories - Low Risk (Score < 10): Standard validation - Medium Risk (10-20): Enhanced validation - High Risk (20-30): Comprehensive validation - Critical Risk (>30): Executive approval required ### Dashboard Components to Generate #### Release Readiness Dashboard Display: - Overall readiness score - Validation status by type - Blocking issues - Risk assessment - Timeline status - Go/no-go recommendation #### Validation Progress Dashboard Show: - Validation checklist - Completion percentage - Pending approvals - Issue tracking - Resource allocation - Critical path items #### Risk Management Dashboard Include: - Risk heat map - Mitigation status - Impact analysis - Contingency readiness - Historical comparisons - Trend analysis ### Approval Workflows #### Standard Approval Chain 1. Technical validation complete 2. QA sign-off 3. Business owner approval 4. Security review 5. Compliance check 6. Final release approval #### Emergency Release Process 1. Critical issue validation 2. Emergency CAB approval 3. Risk acknowledgment 4. Limited testing 5. Executive approval 6. Post-release validation ### Integration Requirements #### Release Management Tools - ServiceNow integration - JIRA release tracking - Azure DevOps boards - Remedy change management - Custom ITSM tools #### Communication Platforms - Slack notifications - Email alerts - Teams updates - SMS for critical - Dashboard widgets #### Documentation Systems - Confluence updates - SharePoint storage - Knowledge base - Training materials - Release notes ### Best Practices to Implement 1. **Validation Standards** - Clear criteria - Objective measures - Automated checks - Documented process - Regular reviews 2. **Risk Management** - Early identification - Mitigation plans - Clear escalation - Regular updates - Lessons learned 3. **Communication** - Stakeholder updates - Clear status reporting - Issue transparency - Timeline management - Success metrics 4. **Continuous Improvement** - Post-release reviews - Process refinement - Automation expansion - Metric tracking - Feedback incorporation ### Advanced Features to Consider 1. **AI-Powered Validation** - Pattern recognition - Risk prediction - Anomaly detection - Smart recommendations - Auto-validation 2. **Predictive Analytics** - Success probability - Issue forecasting - Timeline prediction - Resource optimization - Impact analysis 3. **Intelligent Automation** - Auto-approval routing - Dynamic checklists - Smart notifications - Conditional workflows - Self-healing processes ### Error Handling Instructions Handle these scenarios: 1. Validation failures 2. Missing approvals 3. Dependency issues 4. Timeline conflicts 5. Resource constraints Recovery strategies: - Clear escalation paths - Alternative approvers - Risk acceptance process - Fast-track procedures - Rollback planning ### Testing Requirements Generate test classes for: 1. Validation logic 2. Risk calculations 3. Approval workflows 4. Integration points 5. Dashboard accuracy ### Success Metrics Track and measure: - Release success rate - Validation accuracy - Issue prevention rate - Time to release - Rollback frequency - Stakeholder satisfaction