sf-agent-framework/sf-core/tasks/requirements-analysis.md

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

# Requirements Analysis

## Purpose

Analyze and document comprehensive requirements for Salesforce implementations
to ensure solution alignment with business needs.

## Instructions

1. **Stakeholder Engagement**
   - Identify all stakeholders
   - Conduct interviews
   - Facilitate workshops
   - Gather feedback
   - Document perspectives

2. **Business Requirements**
   - Document business objectives
   - Define success criteria
   - Capture process requirements
   - Identify compliance needs
   - Document constraints

3. **Functional Requirements**
   - Define system capabilities
   - Document user stories
   - Specify acceptance criteria
   - Map process flows
   - Define business rules

4. **Non-Functional Requirements**
   - Performance requirements
   - Security requirements
   - Usability standards
   - Scalability needs
   - Integration requirements

5. **Requirements Prioritization**
   - Apply MoSCoW method
   - Consider business value
   - Assess implementation effort
   - Review dependencies
   - Create priority matrix

6. **Traceability Management**
   - Create traceability matrix
   - Link to design elements
   - Map to test cases
   - Track changes
   - Maintain versions

## Input Requirements

- Business case document
- Stakeholder registry
- Current state analysis
- Process documentation
- Compliance standards
- Technical constraints

## Output Format

- Requirements Package:
  - Requirements document
  - User story backlog
  - Traceability matrix
  - Process diagrams
  - Priority matrix
  - Approval records

## Requirement Types

- **Business**: Strategic objectives
- **Functional**: System capabilities
- **Non-Functional**: Quality attributes
- **Technical**: Platform constraints
- **Regulatory**: Compliance needs
- **Transitional**: Migration needs

## Analysis Techniques

- Stakeholder interviews
- Workshop facilitation
- Process observation
- Document analysis
- Prototype feedback
- Gap analysis

## Best Practices

- Use clear language
- Make requirements testable
- Avoid ambiguity
- Document assumptions
- Validate with stakeholders
- Maintain traceability
- Version control changes