# 139 Document E67a5c86 > Multi-Skill Orchestration: sf-deploy Perspective - Skill: `tools-only/139-document-e67a5c86` (Agent Skill, multi-file: 3 files) - Install (CLI): `npx skillmds@latest add tools-only/139-document-e67a5c86` - Raw SKILL.md: https://api.skillmd.com/api/skills/tools-only/139-document-e67a5c86/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: DevOps & Infra - Author: tools-only (https://skillmd.com/u/tools-only) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/tools-only/139-document-e67a5c86 --- # Multi-Skill Orchestration: sf-deploy Perspective This document details how sf-deploy fits into the multi-skill workflow for Salesforce development. --- ## Standard Orchestration Order ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ STANDARD MULTI-SKILL ORCHESTRATION ORDER │ ├─────────────────────────────────────────────────────────────────────────────┤ │ 1. sf-metadata │ │ └── Create object/field definitions (LOCAL files) │ │ │ │ 2. sf-flow │ │ └── Create flow definitions (LOCAL files) │ │ │ │ 3. sf-deploy ◀── YOU ARE HERE │ │ └── Deploy all metadata (REMOTE) │ │ │ │ 4. sf-data │ │ └── Create test data (REMOTE - objects must exist!) │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ## Why sf-deploy Goes Third (Not Last) sf-deploy is the **bridge** between local files and the org: | Before sf-deploy | After sf-deploy | |------------------|-----------------| | Metadata exists locally | Metadata exists in org | | Flows reference objects | Flows can run | | Data can't be created | sf-data can create records | **sf-data REQUIRES deployed objects**. The error `SObject type 'X' not supported` means objects weren't deployed. --- ## Deploy Order WITHIN sf-deploy When deploying multiple metadata types: ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ INTERNAL DEPLOY ORDER │ ├─────────────────────────────────────────────────────────────────────────────┤ │ 1. Custom Objects & Fields │ │ └── Objects must exist before anything references them │ │ │ │ 2. Permission Sets │ │ └── Field-Level Security requires fields to exist │ │ │ │ 3. Apex Classes │ │ └── @InvocableMethod for Flow actions │ │ │ │ 4. Flows (as Draft) │ │ └── Flows reference fields and Apex │ │ │ │ 5. Activate Flows │ │ └── Change status Draft → Active │ └─────────────────────────────────────────────────────────────────────────────┘ ``` **Why this order?** - Flows need fields to exist - Users need Permission Sets for field visibility - Triggers may depend on active flows - Draft flows can be tested before activation --- ## Integration + Agentforce Extended Order When deploying agents with external API integrations: ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ AGENTFORCE DEPLOYMENT ORDER │ ├─────────────────────────────────────────────────────────────────────────────┤ │ 1. sf-connected-apps → Create OAuth Connected App │ │ 2. sf-integration → Create Named Credential + External Service │ │ 3. sf-apex → Create @InvocableMethod (if needed) │ │ 4. sf-flow → Create Flow wrapper │ │ │ │ 5. sf-deploy ◀── FIRST DEPLOYMENT │ │ └── Deploy: Objects, Fields, Permission Sets, Apex, Flows │ │ │ │ 6. sf-ai-agentscript → Create agent with flow:// target │ │ │ │ 7. sf-deploy ◀── SECOND DEPLOYMENT (Agent Publish) │ │ └── sf agent publish --api-name [AgentName] │ │ │ │ 8. sf-data → Create test data │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ## Common Deployment Errors from Wrong Order | Error | Cause | Fix | |-------|-------|-----| | `Invalid reference: Quote__c` | Object not deployed | Deploy objects first | | `Field does not exist: Status__c` | Field not deployed | Deploy fields first | | `no CustomObject named X found` | Permission Set deployed before object | Deploy objects, then Permission Sets | | `SObject type 'X' not supported` | sf-data ran before deploy | Deploy before creating data | | `Flow is invalid` | Flow references missing object | Deploy objects before flows | | `Flow not found` | Agent references undeploy flow | Deploy flows before agent publish | --- ## Two-Step Deployment Pattern (Recommended) Always validate before deploying: ```bash # Step 1: Dry-run validation sf project deploy start --dry-run --source-dir force-app --target-org alias # Step 2: Actual deployment (only if validation passes) sf project deploy start --source-dir force-app --target-org alias ``` --- ## Cross-Skill Dependencies Before deploying, verify these prerequisites: | Dependency | Check Command | Required For | |------------|---------------|--------------| | TAF Package | `sf package installed list` | TAF trigger pattern | | Custom Objects | `sf sobject describe` | Apex/Flow field refs | | Permission Sets | `sf org list metadata --metadata-type PermissionSet` | FLS for fields | | Flows | `sf org list metadata --metadata-type Flow` | Agent actions | --- ## sf-ai-agentscript Integration For agent deployments, use the specialized commands: ```bash # Deploy dependencies first sf project deploy start --metadata ApexClass,Flow --target-org alias # Validate agent syntax sf agent validate authoring-bundle --api-name AgentName --target-org alias # Publish agent sf agent publish authoring-bundle --api-name AgentName --target-org alias # Activate agent sf agent activate --api-name AgentName --target-org alias ``` --- ## Invocation Patterns | From Skill | To sf-deploy | When | |------------|--------------|------| | sf-metadata | → sf-deploy | "Deploy objects to [org]" | | sf-flow | → sf-deploy | "Deploy flow with --dry-run" | | sf-apex | → sf-deploy | "Deploy classes with RunLocalTests" | | sf-ai-agentscript | → sf-deploy | "Deploy and publish agent" | --- ## Related Documentation | Topic | Location | |-------|----------| | Deployment workflows | `sf-deploy/examples/deployment-workflows.md` | | Agent deployment guide | `sf-deploy/docs/agent-deployment-guide.md` | | Deploy script template | `sf-deploy/examples/deploy.sh` |