sf-agent-framework/sf-core/tasks/design-validation.md

AI Agent Orchestration Framework for Salesforce Development - Two-phase architecture with 70% context reduction

# Design Validation

## Purpose

Validate Salesforce solution designs against requirements, best practices, and
technical constraints before implementation begins.

## Instructions

1. **Requirements Traceability**
   - Map design elements to requirements
   - Verify complete requirement coverage
   - Identify gaps or missing elements
   - Validate acceptance criteria
   - Confirm stakeholder alignment

2. **Technical Design Review**
   - Assess solution architecture
   - Validate data model design
   - Review security implementation
   - Check integration approaches
   - Verify scalability considerations

3. **Best Practices Assessment**
   - Compare against Salesforce standards
   - Review declarative vs code decisions
   - Assess configuration choices
   - Validate naming conventions
   - Check reusability patterns

4. **Constraint Validation**
   - Verify governor limit compliance
   - Check license requirements
   - Validate storage projections
   - Assess API limit impacts
   - Review feature dependencies

5. **Risk Assessment**
   - Identify technical risks
   - Evaluate complexity factors
   - Assess maintenance burden
   - Review upgrade impacts
   - Consider technical debt

6. **Prototype Validation**
   - Build proof of concepts
   - Test critical assumptions
   - Validate performance claims
   - Verify integration points
   - Demonstrate key features

## Input Requirements

- Solution design documents
- Requirements traceability matrix
- Technical architecture diagrams
- Data model specifications
- Integration design documents
- Security design artifacts

## Output Format

- Design Validation Report including:
  - Validation summary
  - Requirements coverage analysis
  - Technical assessment results
  - Risk identification matrix
  - Recommendations
  - Approval checklist

## Validation Criteria

- **Functional Completeness**: All requirements addressed
- **Technical Feasibility**: Solution is implementable
- **Performance Viability**: Meets performance needs
- **Security Adequacy**: Satisfies security requirements
- **Maintainability**: Long-term sustainability
- **Scalability**: Supports growth projections

## Review Checkpoints

- Conceptual design approval
- Logical design validation
- Physical design review
- Security design verification
- Integration design confirmation
- Final design sign-off

## Best Practices

- Involve all stakeholders
- Use design review templates
- Document assumptions clearly
- Test critical paths early
- Consider future phases
- Balance ideal vs practical
- Maintain design traceability