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/well-architected.md
View on GitHub# Well-Architected Mapping: Change Management and Deployment
## Pillars Addressed
### Operational Excellence
Release methods, approvals, and validation steps are core operating mechanisms, not paperwork.
- Source-driven deployment reduces manual variance.
- Checklists and promotion rules make releases repeatable.
### Reliability
Reliable releases depend on realistic validation and credible rollback.
- Explicit sequencing reduces surprise regressions.
- Smoke tests and rollback plans shorten incident duration when things go wrong.
### Security
Permissions, sharing, and integration metadata often ride in deployments and need tighter review than ordinary layout changes.
- High-risk metadata gets explicit scrutiny before promotion.
- Environment-aligned auth and permission handling reduces accidental exposure.
## Pillars Not Addressed
- **User Experience** - this skill improves user outcomes indirectly through safer releases, not through interface design itself.
- **Scalability** - the emphasis is release discipline rather than runtime scale design.
## Official Sources Used
- Metadata API Developer Guide, `deploy()` → `DeployOptions`
(https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/api_meta.pdf) —
`checkOnly`, `rollbackOnError` ("must be set to `true` if you're deploying to a
production org"), `purgeOnDelete`, `ignoreWarnings`, `allowMissingFiles`,
`performRetrieve`, `singlePackage`, and the `testLevel` enum with its per-environment
defaults. Grounds "The Deploy Contract" in SKILL.md, `references/metadata-examples.md`
§3, and the `rollbackOnError`, test-level, `purgeOnDelete`, and Master-Detail gotchas.
- Metadata API Developer Guide, "Deleting Components from an Organization" — the
`destructiveChanges.xml` / `destructiveChangesPre.xml` / `destructiveChangesPost.xml`
contract, the companion `package.xml` requirement, the no-wildcards rule, and
"post destructive changes are processed before running any tests". Grounds
`references/metadata-examples.md` §2 and the destructive-manifest gotcha.
- Metadata API Developer Guide, `deployRecentValidation()` and "Deploy a Recently
Validated Component Set Without Tests" — the ten-day quick-deploy window, the
target-environment constraint, and the two coverage rules. Grounds the quick-deploy
gotcha and the validate → quick → report sequence.
- Metadata API Developer Guide, "Deploying and Retrieving Metadata with the Zip File",
`DeployResult`, `DeployMessage`, `RunTestsResult`, `cancelDeploy()`, and the
Deployment Status / deploy-limits sections of `deploy()` — the manifest element
reference, the nine-value `DeployStatus` enum including `SucceededPartial`, the fields
to read when verifying a release, the write-lock and single-concurrent-deploy
behaviour, and the absence of any reverse operation. Grounds
`references/metadata-examples.md` §1, §5, §6 and the concurrency gotcha.
- Metadata API Developer Guide, Profile metadata type — "We designed Profile metadata
deployment to overlay the existing Profile settings in a target org". Grounds the
"Profiles are release debt" guardrail; the mechanism itself is owned by
`admin/permission-sets-vs-profiles`, which this skill defers to rather than restates.
- Metadata API Developer Guide, FlowDefinition and Flow metadata types — "If you deploy
with flow definitions, the active version numbers in the flow definitions override the
`status` fields in the flows", plus the `FlowVersionStatus` values. Grounds the Flow
activation gotcha.
- Salesforce App Limits Cheat Sheet, Metadata Limits and Apex Governor Limits
(https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf)
— 10,000 files per deploy or retrieve, ~39 MB compressed / 600 MB uncompressed, 10,000
files per inbound or outbound change set, and 7,500 class and trigger code units per
Apex deployment. Grounds the deploy-size gotcha and the Change Set ceiling.
- Salesforce Object Reference, `DevopsEnvDeployment`
(https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/object_reference.pdf)
— a queryable record of DevOps Center promotions with `DeployStatus` and
`CheckDeployStatus` picklists, API version 66.0 and later. Grounds the SOQL
verification in `references/metadata-examples.md` §5.
- Salesforce Well-Architected — operational-quality framing for release design; supports
the Operational Excellence and Reliability sections above.
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 |