PranavNagrecha/AwesomeSalesforceSkills / skills/admin/change-management-and-deployment
change-management-and-deployment
VerifiedUse when planning, reviewing, or troubleshooting Salesforce metadata releases and admin deployment processes. Triggers: 'change set', 'deployment plan', 'rollback', 'DevOps Center', 'SFDX deploy', 'release checklist', 'production deployment', 'validation only deploy', 'quick deploy', 'test level', 'rollbackOnError', 'destructive changes', 'package.xml for an admin release', 'deployment status'. NOT for change set upload mechanics — use devops/change-set-deployment. NOT for scoring release risk up front — use admin/deployment-risk-assessment.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.2 KB |
| references/examples.md | markdown | 3.4 KB |
| references/gotchas.md | markdown | 13.1 KB |
| references/llm-anti-patterns.md | markdown | 7.5 KB |
| references/metadata-examples.md | markdown | 17.9 KB |
| references/well-architected.md | markdown | 4.4 KB |
| scripts/check_deployment_manifest.py | script | 15.4 KB |
| templates/release-plan-template.md | markdown | 7.5 KB |
references/examples.md
View on GitHub# Examples: Change Management and Deployment
---
## Example: Small Admin Hotfix
**Scenario:** A validation rule typo is blocking Case creation in production. The admin team has connected sandboxes but no source-driven release process yet.
**Decision:** Use a tightly scoped Change Set for the hotfix, document the change, and update source afterward.
**Why this is acceptable:** The release is small, urgent, and low in dependency complexity.
**What would be wrong:** treating that success as proof that weekly multi-feature releases should stay on Change Sets forever.
---
## Example: Moving from Change Sets to DevOps Center
**Scenario:** An admin team deploys page layouts, fields, flows, and permission sets every sprint. Releases are manual and regression-prone.
**Decision:** Move to DevOps Center with source-tracked Developer sandboxes and a simple Sandbox -> Production promotion path.
**Why:** The team needs Git-backed promotion discipline and review, but not a fully custom CI/CD program on day one.
---
## Example: Metadata Release Coupled to Data Cutover
**Scenario:** A release adds new Opportunity stages, validation rules, and a bulk update to open Opportunities.
**Release handling:**
1. deploy metadata to lower environments
2. rehearse data load and reconciliation
3. define production sequence explicitly
4. keep data rollback separate from metadata rollback
**The deploy contract, written down before the window.** This is what the release plan
hands to whoever runs the pipeline. Every value is chosen; none is left to a default.
```yaml
release: 2026-09-12-opportunity-stage-realignment
target_org: production
vehicle: sf CLI # decision matrix row 3 - weekly cadence, 4 environments
deploy_options:
checkOnly: true # pass 1 only; pass 2 is a quick deploy of this validation
rollbackOnError: true # required in production; set explicitly in sandbox too
testLevel: RunLocalTests
runTests: [] # empty - only read when testLevel is RunSpecifiedTests
purgeOnDelete: false # inert in production anyway; deletions go to the Recycle Bin
ignoreWarnings: false
allowMissingFiles: false # the guide says do not set this for production
manifests:
package: manifest/package.xml
destructive_pre: null
destructive_post: manifest/destructiveChangesPost.xml # retires Stage_Legacy__c
validation:
run_on: 2026-09-09 # 3 days before the window
expires_on: 2026-09-19 # 10-day quick-deploy clock
target: production # NOT staging - a staging validation licenses nothing here
sequence:
1_metadata: "validated package, quick deploy"
2_data: "bulk update of open Opportunities - separate job, separate owner"
3_activation: "activate Opportunity_Stage_Router flow"
backout:
metadata: "redeploy manifest/pre-release/ (retrieved 2026-09-08, before any change)"
data: "restore StageName from the pre-load export - NOT covered by the metadata backout"
fastest: "deactivate Opportunity_Stage_Router; leaves fields in place, stops the behaviour"
```
**Lesson:** one release window can contain both metadata and data, but they must not share one vague rollback sentence. Note that `backout.metadata` and `backout.data` are two different jobs with two different owners — redeploying the old manifest does not un-edit the records the release touched.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |