sf-agent-framework

workflow: id: project-kickoff name: Project Kickoff Workflow description: >- Comprehensive project initiation and team alignment workflow for Salesforce implementations. Ensures all teams are aligned, prepared, and have clear understanding of project goals and approach. type: sequential duration: 2-3 weeks project_types: - new-implementation - major-enhancement - platform-migration - multi-cloud-deployment sequence: # Phase 1: Project Initiation (Days 1-3) - phase: project_initiation duration: 3 days steps: - step: project_charter_creation agent: sf-orchestrator participants: all_team creates: project-charter.md uses: templates/project-charter-tmpl activities: - Create project charter document - Define project scope and objectives - Identify key stakeholders - Establish success criteria - Set project timeline deliverables: - project_charter.md - stakeholder_matrix.xlsx - success_metrics.md - step: technical_discovery agent: sf-architect participants: [ sf-admin, sf-solution-architect, sf-data-architect, sf-technical-architect, sf-security-architect, sf-integration-architect, ] creates: technical-landscape.md uses: solution-design activities: - Review existing system architecture - Identify integration points - Assess data volumes - Evaluate security requirements - Document technical constraints deliverables: - technical_landscape.md - integration_inventory.xlsx - security_assessment.md - step: business_requirements_gathering agent: sf-business-analyst participants: [sf-translator, business_stakeholders, sf-product-owner, sf-product-manager] creates: business-requirements.md uses: requirement-elicitation activities: - Conduct stakeholder interviews - Document current processes - Identify pain points - Define future state vision - Prioritize requirements deliverables: - business_requirements.md - process_maps/ - pain_points_register.xlsx # Phase 2: Team Alignment (Days 4-5) - phase: team_alignment duration: 2 days steps: - step: solution_alignment_workshop agent: sf-solution-architect participants: all_technical_team duration: 4 hours creates: solution-approach.md activities: - Present technical landscape - Discuss solution options - Align on technical approach - Identify technical risks - Define architecture principles deliverables: - solution_approach.md - technical_risks.md - architecture_principles.md - step: project_planning_session agent: sf-orchestrator participants: all_team duration: 4 hours creates: project-plan.md activities: - Define project phases - Create high-level timeline - Identify milestones - Assign team responsibilities - Establish communication plan deliverables: - project_plan.md - team_raci_matrix.xlsx - communication_plan.md - step: devops_setup_planning agent: sf-devops-lead participants: [sf-developer, sf-admin] creates: devops-strategy.md condition: greenfield_or_major_project activities: - Define environment strategy - Plan CI/CD pipeline - Establish branching strategy - Set deployment approach - Configure monitoring deliverables: - devops_strategy.md - environment_plan.md - pipeline_design.md # Phase 3: Detailed Planning (Days 6-10) - phase: detailed_planning duration: 5 days parallel_tracks: - track: functional_design lead: sf-business-analyst steps: - step: user_story_creation creates: initial-backlog.md uses: user-story-creation notes: Create initial set of user stories from requirements - step: process_design creates: process-designs/ uses: process-mapping notes: Design future state processes - track: technical_design lead: sf-architect steps: - step: data_model_design agent: sf-data-architect creates: data-model.md uses: data-model-design notes: Design custom objects and relationships - step: integration_design agent: sf-integration-architect creates: integration-design.md uses: integration-planning condition: has_integrations notes: Design integration architecture - track: security_planning lead: sf-security-architect steps: - step: security_model_design creates: security-model.md uses: access-model-design notes: Design profiles, permission sets, sharing - step: compliance_planning creates: compliance-plan.md uses: compliance-check condition: has_compliance_requirements notes: Plan for regulatory compliance # Phase 4: Kickoff Execution (Days 11-15) - phase: kickoff_execution duration: 5 days steps: - step: formal_project_kickoff agent: sf-orchestrator participants: [all_team, all_stakeholders] duration: 2 hours activities: - Present project charter - Review timeline and milestones - Confirm roles and responsibilities - Address questions and concerns - Get formal approval to proceed deliverables: - kickoff_presentation.pptx - meeting_minutes.md - approval_confirmation.md - step: team_enablement parallel: true activities: - track: technical_enablement agent: sf-architect participants: technical_team duration: 4 hours topics: - Solution architecture walkthrough - Development standards - Code review process - Testing approach - track: functional_enablement agent: sf-business-analyst participants: functional_team duration: 4 hours topics: - Business process overview - User story standards - Acceptance criteria guidelines - UAT approach - step: environment_setup agent: sf-admin participants: [sf-developer, sf-devops-lead] creates: environment-setup-log.md activities: - Create development sandboxes - Set up version control access - Configure CI/CD pipeline - Install required tools - Verify team access deliverables: - environment_setup_log.md - access_verification.xlsx - tools_checklist.md - step: sprint_zero_planning agent: sf-orchestrator participants: all_team creates: sprint-zero-plan.md activities: - Define sprint zero objectives - Create initial sprint backlog - Set up tracking tools - Schedule recurring meetings - Establish team norms deliverables: - sprint_zero_plan.md - meeting_schedule.md - team_working_agreement.md # Phase 5: Project Launch (Day 15) - phase: project_launch duration: 1 day steps: - step: go_no_go_decision agent: sf-orchestrator participants: [sf-architect, sf-business-analyst, steering_committee] creates: launch-decision.md activities: - Review readiness checklist - Confirm all prerequisites met - Address any blockers - Get formal go decision - Communicate to all stakeholders - step: project_launch_communication agent: sf-orchestrator activities: - Send project launch email - Update project portal - Set up status reporting - Activate monitoring dashboards - Begin daily standups deliverables: - launch_communication.md - status_report_template.md - dashboard_links.md success_criteria: - All team members onboarded and enabled - Project charter approved by stakeholders - Technical approach validated and documented - Development environments ready - Initial backlog created and prioritized - Team norms and processes established - All stakeholders aligned on objectives deliverables_summary: governance: - Project charter - Stakeholder matrix - RACI matrix - Communication plan technical: - Solution architecture - Technical design documents - DevOps strategy - Security model functional: - Business requirements - Process designs - Initial user stories - Success metrics operational: - Project plan - Team working agreement - Environment setup guide - Meeting schedule