PranavNagrecha/AwesomeSalesforceSkills / skills/admin/deployment-risk-assessment
deployment-risk-assessment
VerifiedUse when a practitioner needs to classify the risk level of an upcoming Salesforce deployment, define rollback trigger conditions, or assign decision authority before the release window opens. Triggers: 'how risky is this release', 'what needs rollback planning', 'classify deployment risk', 'pre-deployment risk checklist', 'rollback decision authority', 'high risk metadata types'. NOT for executing the deployment itself, writing CI/CD pipeline code, or troubleshooting failures after a deployment has already run — use admin/change-management-and-deployment for execution planning and devops/deployment-error-troubleshooting for post-failure diagnosis.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.5 KB |
| references/examples.md | markdown | 4.9 KB |
| references/gotchas.md | markdown | 5.7 KB |
| references/llm-anti-patterns.md | markdown | 9.6 KB |
| references/well-architected.md | markdown | 5.2 KB |
| scripts/check_deployment_risk_assessment.pyexecutable | script | 10.5 KB |
| templates/deployment-risk-assessment-template.md | markdown | 4.5 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — Deployment Risk Assessment
## Relevant Pillars
- **Reliability** — Primary pillar for this skill. The Well-Architected Reliable pillar defines reliable systems as those that can withstand failure and recover gracefully. Deployment risk assessment is a pre-release reliability practice: it identifies what could fail, ensures rollback paths are real rather than hypothetical, and ensures the team can recover within an acceptable time window. Without pre-deployment risk classification, a team discovers its rollback assumptions during a production incident rather than before it.
- **Operational Excellence** — Risk classification, rollback runbooks, and go/no-go criteria are operational process artifacts. The Well-Architected framework explicitly calls for documented change procedures, defined escalation paths, and post-release verification as elements of operational excellence. This skill operationalizes those requirements into concrete pre-deployment artifacts.
- **Security** — Security metadata (PermissionSets, Profiles, SharingRules, ConnectedApps, AuthProviders) consistently receives HIGH risk classification because misconfiguration can silently over-share or under-share access at org-wide scale. The risk assessment process surfaces these components for explicit scrutiny rather than treating them as equivalent to layout changes.
- **Performance** — Indirectly relevant. HIGH-risk deployments that include bulk-affecting automation (Record-Triggered Flows, Apex triggers on high-volume objects) are assessed for governor limit exposure and bulk-execution behavior as part of classification. A deployment that passes functional validation in a low-data sandbox may perform differently at production data volumes.
- **Scalability** — Indirectly relevant. Risk classification considers whether components have been validated against representative data volumes, which is a scalability readiness check embedded in the pre-deployment process.
## Architectural Tradeoffs
**Rollback fidelity vs. deployment speed:** The fastest deployment method (direct org config in Setup) has the worst rollback fidelity — no artifact, no version, no automated undo path. The slowest path to initial setup (unlocked packages with version management) provides the best rollback fidelity. Teams must decide where they sit on this spectrum. The Well-Architected Resilient guidance recommends preferring packaged deployments for HIGH-risk changes precisely because version-based rollback is faster and more reliable than re-deploying manually captured metadata.
**Risk decomposition vs. release velocity:** Decomposing a large release into smaller, lower-risk releases reduces the blast radius of any single failure and makes rollback cheaper. This trades release velocity for reliability. The Well-Architected framework favors smaller, more frequent releases over large infrequent ones for this reason. Risk classification often surfaces bundled releases that should be split.
**Pre-deployment preparation time vs. release window length:** Investing time in pre-deployment risk classification, rollback runbook authoring, and destructive change preparation reduces the expected duration and complexity of rollback execution if it is needed. Teams that skip this preparation get faster deployment window starts but longer, more chaotic recovery events.
## Anti-Patterns
1. **Treating risk assessment as optional for "simple" releases** — The decision that a release is simple enough to skip risk assessment is itself a risk classification decision made without a framework. Practitioners consistently underestimate risk for UI-adjacent changes that have hidden automation dependencies. A required lightweight classification process (even a five-minute review against the HIGH / MEDIUM / LOW criteria) catches the hidden dependencies that intuition misses.
2. **Defining rollback trigger conditions under pressure** — Deciding whether the current production symptoms justify a rollback during an incident introduces human judgment bias, communication overhead, and time delay at the worst possible moment. Pre-agreed observable trigger conditions (error rate, exception type, latency threshold) allow the rollback call to be made by comparing observed data against a pre-written standard, not by negotiating under pressure.
3. **Relying on sandbox state as a rollback source** — Some teams plan to retrieve from a Full sandbox if rollback is needed, assuming the sandbox reflects production. Sandbox state diverges from production every time a production-only change is made outside the sandbox track. A rollback plan that depends on sandbox state is unreliable by design. The rollback artifact must be a production retrieve taken immediately before the deployment window.
## Official Sources Used
- Salesforce Well-Architected: Reliable Pillar — https://architect.salesforce.com/well-architected/trusted/reliable
- Salesforce Well-Architected: Resilient (Adaptable Pillar) — https://architect.salesforce.com/well-architected/adaptable/resilient
- Metadata API Developer Guide — https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_intro.htm
- Salesforce Well-Architected Overview — https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |