sf-agent-framework/sf-core/manifest.yaml

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

name: sf-core
version: 4.1.1
short-title: Salesforce Two-Phase Development Framework with 70% Context Reduction
description: >-
  Revolutionary SF-Agent framework v4.0 featuring two-phase development architecture that reduces 
  context usage by 70% and delivers 3x faster implementation. Includes 30+ specialized agents with 
  6 lean variants for development phase, story-based context engineering, enhanced template system v2.0 
  with LLM instructions, and phase-aware workflows. Maintains full backwards compatibility while 
  providing 85% first-pass accuracy and comprehensive OmniStudio & MCP support.
author: SF-Agent Framework Extensions Team
sf-agent_version: 4.1.1

# Files to create in the expansion pack
files:
  agents:
    # Product Team (4 agents)
    - sf-product-manager.md # Rachel Chen - Product Strategy & Vision
    - sf-product-owner.md # Marcus Thompson - Product Ownership & Backlog
    - sf-business-analyst.md # Emily Watson - Business Analysis & Requirements
    - sf-ux-expert.md # Sofia Martinez - User Experience Design

    # Core Team (7 agents)
    - sf-orchestrator.md # Alex Chen - Salesforce Delivery Manager
    - sf-admin.md # Maria Rodriguez - Senior Administrator
    - sf-developer.md # Jordan Davis - Lead Developer
    - sf-architect.md # Sarah Johnson - Solution Architect
    - sf-qa.md # Michael Brown - QA Automation Engineer
    - sf-release-manager.md # Emma Wilson - Release Manager
    - sf-trainer.md # Lisa Anderson - Training & Enablement Specialist

    # Architecture Team (6 agents)
    - sf-chief-architect.md # Chief Architect - Enterprise Architecture Vision
    - sf-solution-architect.md # Solution Architect - Business-Technical Bridge
    - sf-technical-architect.md # Technical Architect - Platform Excellence
    - sf-data-architect.md # Data Architect - Data Strategy & Governance
    - sf-integration-architect.md # Integration Architect - System Connectivity
    - sf-security-architect.md # Security Architect - Security & Compliance

    # Data Team (4 agents)
    - sf-data-migration-specialist.md # David Chen - Data Migration Expert
    - sf-data-quality-analyst.md # Priya Sharma - Data Quality & Governance
    - sf-data-validation-engineer.md # Robert Kim - Data Validation & Testing
    - sf-etl-developer.md # Amanda Liu - ETL Development & Integration

    # Deployment Team (4 agents)
    - sf-build-engineer.md # Tom Zhang - Build Automation Engineer
    - sf-release-automation.md # Nina Kowalski - Release Automation Engineer
    - sf-devops-lead.md # DevOps Lead - CI/CD & Automation
    - sf-security.md # Jennifer Walsh - Security & Compliance Officer

    # Lean Agent Variants (6 agents - v4.0)
    - sf-developer-lean.md # Lean Developer - 32k context, 3x faster
    - sf-admin-lean.md # Lean Admin - 24k context, 2.5x faster
    - sf-qa-lean.md # Lean QA - 24k context, 2x faster
    - sf-build-engineer-lean.md # Lean Build Engineer - 20k context, 3x faster
    - sf-release-automation-lean.md # Lean Release Automation - 28k context, 2.5x faster
    - sf-devops-lead-lean.md # Lean DevOps Lead - 30k context, 2x faster

    # Specialty Experts (5 agents)
    - sf-omnistudio-architect.md # OmniStudio Architect - Digital Experience Expert
    - sf-mcp-architect.md # Dr. Elena Martinez - MCP Integration Architect
    - sf-translator.md # Chris Anderson - Technical Solutions Translator
    - sf-coe-director.md # CoE Director - Center of Excellence Lead
    - sf-platform-owner.md # Platform Owner - Strategic Platform Management

  data:
    - salesforce-best-practices.md # Comprehensive best practices guide
    - salesforce-terminology.md # Platform terminology and jargon
    - salesforce-release-notes.md # Current platform updates and changes
    - omnistudio-architecture.md # OmniStudio architecture knowledge base
    - omnistudio-best-practices.md # OmniStudio implementation guidelines
    - omnistudio-patterns.md # Design patterns for OmniStudio
    - deployment-patterns.md # Deployment patterns and strategies
    - risk-mitigation-strategies.md # Risk management strategies
    - communication-templates.md # Stakeholder communication templates
    - mcp-patterns.md # Model Context Protocol patterns

  tasks:
    # Core utilities (REQUIRED)
    - create-doc.md # Document creation from templates
    - create-doc-v2.md # Enhanced document creation with LLM instructions (v4.0)
    - execute-checklist.md # Checklist validation system
    - generate-story-context.md # Story-based context generation (v4.0)
    # Salesforce-specific tasks
    - advanced-elicitation.md # Requirements gathering
    - flow-builder.md # Flow creation and documentation
    - permission-set-config.md # Permission set configuration
    - apex-class-generator.md # Apex class generation
    - apex-class-generator-v2.md # Story-based Apex generation (v4.0)
    - lwc-component-builder.md # LWC component creation
    - lwc-component-builder-v2.md # Story-based LWC generation (v4.0)
    - test-class-creator.md # Test class generation
    - test-class-creator-v2.md # Story-based test generation (v4.0)
    - deployment-orchestration-v2.md # Story-based deployment (v4.0)
    - solution-design.md # Technical solution design
    - requirement-elicitation.md # Business requirements gathering
    - pipeline-setup.md # CI/CD pipeline configuration
    - security-audit.md # Security assessment
    - flow-to-apex.md # Convert Flow to Apex
    - deployment-automation.md # Deployment automation
    - org-setup.md # Initial org configuration
    - omnistudio-design.md # OmniStudio solution design
    - flexcard-development.md # FlexCard component development
    - omniscript-builder.md # OmniScript workflow creation
    - integration-procedure-design.md # Integration Procedure implementation
    - dataraptor-configuration.md # DataRaptor setup and optimization
    - omnistudio-performance-tuning.md # OmniStudio performance optimization
    - mcp-server-setup.md # MCP server configuration
    - mcp-integration.md # MCP integration architecture

  utils:
    # Core utilities (REQUIRED)
    - template-format.md # Template markup conventions
    - workflow-management.md # Workflow orchestration system

  templates:
    - apex-class-tmpl.md # Apex class template
    - lwc-component-tmpl.md # LWC component template
    - flow-documentation-tmpl.md # Flow documentation
    - user-story-tmpl.md # User story template
    - technical-design-tmpl.md # Technical design document
    - deployment-runbook-tmpl.md # Deployment procedures
    - test-plan-tmpl.md # Test plan template
    - security-audit-tmpl.md # Security audit report
    - permission-matrix-tmpl.md # Permission matrix
    - integration-spec-tmpl.md # Integration specification
    - flexcard-spec-tmpl.md # FlexCard specification template
    - omniscript-design-tmpl.md # OmniScript design document
    - integration-procedure-tmpl.md # Integration Procedure template
    - dataraptor-mapping-tmpl.md # DataRaptor mapping template
    - omnistudio-architecture-tmpl.md # OmniStudio architecture document
    - mcp-server-tmpl.md # MCP server template
    - mcp-client-config-tmpl.md # MCP client configuration template

  checklists:
    - deployment-readiness-checklist.md # Pre-deployment validation
    - code-review-checklist.md # Apex code quality
    - security-compliance-checklist.md # Security best practices
    - flow-best-practices-checklist.md # Flow standards
    - integration-testing-checklist.md # Integration validation
    - user-story-quality-checklist.md # Story completeness
    - architecture-review-checklist.md # Design validation
    - data-migration-checklist.md # Data quality
    - omnistudio-design-checklist.md # OmniStudio design review
    - flexcard-review-checklist.md # FlexCard quality checklist
    - omniscript-testing-checklist.md # OmniScript testing validation
    - omnistudio-performance-checklist.md # Performance optimization checklist
    - omnistudio-deployment-checklist.md # OmniStudio deployment readiness
    - mcp-security-checklist.md # MCP security validation

  workflows:
    # Phase-Aware Workflows (v4.0)
    - salesforce-two-phase-implementation.yaml # Two-phase development workflow
    - salesforce-greenfield-fullstack-v2.yaml # Phase-aware greenfield
    - salesforce-org-enhancement-v2.yaml # Phase-aware enhancement
    - salesforce-org-modernization-v2.yaml # Phase-aware modernization
    # Classic Workflows (v1 - backwards compatible)
    - agile-sprint.yaml # Agile sprint workflow
    - integration-development.yaml # Integration development workflow
    - project-kickoff.yaml # Project initiation workflow
    - release-deployment.yaml # Deployment workflow
    - security-audit-workflow.yaml # Security assessment workflow
    - salesforce-greenfield-fullstack.yaml # New implementation
    - salesforce-brownfield-enhancement.yaml # Existing org enhancement
    - salesforce-devops-cicd.yaml # DevOps CI/CD workflow
    - salesforce-architecture-review.yaml # Architecture review workflow
    - salesforce-data-migration.yaml # Data migration workflow
    - salesforce-center-of-excellence.yaml # CoE establishment workflow
    - omnistudio-implementation.yaml # OmniStudio implementation workflow
    - omnistudio-optimization.yaml # Performance optimization workflow
    - omnistudio-troubleshooting.yaml # Troubleshooting guide workflow
    - salesforce-mcp-implementation.yaml # MCP implementation workflow
    - salesforce-org-enhancement.yaml # Org enhancement workflow
    - salesforce-org-modernization.yaml # Org modernization workflow

  agent-teams:
    - salesforce-core-team-v2.yaml # Phase-aware core team (v4.0)
    - salesforce-product-team.yaml # Product strategy and design team
    - salesforce-core-team.yaml # Core development team
    - salesforce-architecture-team.yaml # Architecture review team
    - salesforce-data-team.yaml # Data architecture and migration team
    - salesforce-deployment-team.yaml # Deployment and release team
    - salesforce-devops-team.yaml # DevOps and CI/CD team
    - salesforce-governance-team.yaml # CoE and governance team
    - salesforce-enterprise-team.yaml # Complete enterprise team (all 30 agents)

# Data files users must provide
required_user_data:
  - filename: salesforce-org-config.yaml
    description: Organization configuration including org ID, API version, and enabled features
    format: YAML with nested structure
    example: |
      orgId: "00D..."
      apiVersion: "63.0"
      features:
        - Flow
        - LWC
        - Platform Events
      edition: "Enterprise"
    validation: Must include orgId, apiVersion, and features array

  - filename: object-schema.json
    description: Custom objects and fields exported from Schema Builder or Metadata API
    format: JSON with object definitions
    example: |
      {
        "Account": {
          "fields": {
            "Industry": "Picklist",
            "CustomField__c": "Text(255)"
          }
        }
      }
    validation: Valid JSON with at least one object definition

  - filename: code-standards.md
    description: Organization's coding standards and naming conventions
    format: Markdown with sections for different standards
    example: |
      ## Apex Standards
      - Classes: PascalCase
      - Methods: camelCase
      - Constants: UPPER_SNAKE_CASE
    validation: Must include Apex naming conventions

  - filename: deployment-environments.yaml
    description: Environment configurations for all orgs
    format: YAML with environment details
    example: |
      dev:
        url: dev.salesforce.com
        type: sandbox
        refreshDate: 2024-01-15
      prod:
        url: company.my.salesforce.com
        type: production
    validation: Must include at least dev and prod environments

# Knowledge base files embedded in expansion pack
embedded_knowledge:
  - salesforce-best-practices.md
  - salesforce-terminology.md
  - salesforce-release-notes.md
  - omnistudio-architecture.md
  - omnistudio-best-practices.md
  - omnistudio-patterns.md
  - mcp-patterns.md

# Dependencies on core SF-Agent components
core_dependencies:
  agents:
    - architect # For system design reviews
    - developer # For code quality assessments
    - qa-specialist # For testing strategies
  tasks:
    - advanced-elicitation # From core SF-Agent
  workflows:
    - agile-development # Base agile workflow

# Agent interaction patterns
agent_coordination:
  orchestrator: sf-orchestrator
  handoff_protocols: true
  numbered_options: true
  quality_integration: comprehensive
  decision_trees: true

# Character personas
agent_personas:
  sf-orchestrator:
    name: Alex Chen
    role: Salesforce Delivery Manager
    style: Professional, agile-focused, encouraging
  sf-admin:
    name: Maria Rodriguez
    role: Senior Salesforce Administrator
    style: Detail-oriented, declarative-first mindset
  sf-developer:
    name: Jordan Davis
    role: Lead Salesforce Developer
    style: Technical, best-practices focused
  sf-architect:
    name: Dr. Priya Patel
    role: Principal Salesforce Architect
    style: Strategic, Well-Architected principles
  sf-analyst:
    name: Marcus Thompson
    role: Senior Business Analyst
    style: Business-focused, requirements expert
  sf-devops:
    name: Sarah Kim
    role: DevOps Engineering Lead
    style: Automation-focused, efficiency-driven
  sf-qa:
    name: David Martinez
    role: QA Automation Engineer
    style: Quality-obsessed, detail-oriented
  sf-security:
    name: Jennifer Walsh
    role: Security & Compliance Officer
    style: Risk-aware, compliance-focused
  sf-translator:
    name: Chris Anderson
    role: Technical Solutions Consultant
    style: Bridge-builder, optimization expert
  sf-omnistudio-architect:
    name: OmniStudio Maestro
    role: Salesforce OmniStudio Architect
    style: Innovation-driven, user-centric, performance-focused
  sf-mcp-architect:
    name: Dr. Elena Martinez
    role: Salesforce MCP Integration Architect
    style: AI-focused, protocol-driven, enterprise-minded

# Quality standards
quality_standards:
  code_coverage: 85
  deployment_success_rate: 98
  security_scan_pass: 100
  performance_baseline: "sub-3-second page loads"

# Post-install message
post_install_message: |
  🚀 Salesforce SF-Agent Extension Pack Activated!

  Welcome to your Salesforce development team:

  🎯 ORCHESTRATOR: Alex Chen (sf-orchestrator)
     Your Salesforce Delivery Manager who coordinates the entire team

  👥 SPECIALIST AGENTS: 10 domain experts ready to assist
     - Maria Rodriguez: Declarative development & administration
     - Jordan Davis: Apex, LWC, and custom development
     - Dr. Priya Patel: Architecture and solution design
     - Marcus Thompson: Requirements and business analysis
     - Sarah Kim: DevOps and deployment automation
     - David Martinez: Quality assurance and testing
     - Jennifer Walsh: Security and compliance
     - Chris Anderson: Declarative-to-code translation
     - OmniStudio Maestro: FlexCards, OmniScripts, and digital experiences
     - Dr. Elena Martinez: MCP integration and AI connectivity

  📋 FEATURES:
     - 23 Salesforce-specific tasks (including OmniStudio & MCP)
     - 17 intelligent templates with LLM embedding
     - 14 multi-level quality checklists
     - 9 complete workflows
     - 7 team configurations
     - MCP server integration support

  ⚡ QUICK START:
  1. Add required data files to sf-core/data/:
     - salesforce-org-config.yaml
     - object-schema.json
     - code-standards.md
     - deployment-environments.yaml

  2. Launch the orchestrator:
     npm run agent sf-orchestrator

  3. Alex will guide you through:
     - Project type selection
     - Team member introduction
     - Workflow initialization
     - Quality gate setup

  💡 TIPS:
     - Use *help to see all available commands
     - Each agent uses numbered options for easy selection
     - Workflows include decision trees for complex scenarios
     - Quality checklists ensure production-ready deliverables

  🔗 EMBEDDED KNOWLEDGE:
     - Salesforce best practices and patterns
     - Complete terminology guide
     - Current release notes and deprecations
     - OmniStudio architecture and implementation guide
     - Digital experience design patterns
     - Performance optimization strategies
     - Model Context Protocol (MCP) integration patterns
     - AI-to-Salesforce connectivity guides

  Ready to build amazing Salesforce solutions? Let's get started!