Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/deployment-risk-assessment

deployment-risk-assessment

Verified

Use 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.

templates/deployment-risk-assessment-template.md

View on GitHub
# Deployment Risk Assessment — Work Template

Use this template when assessing the risk of an upcoming Salesforce production deployment.
Fill every section before the deployment window opens. Incomplete sections block go/no-go sign-off.

---

## Scope

**Release name / ticket:**
**Deployment date and window:**
**Deployment method:** (Change Sets / DevOps Center / SFDX CLI / Unlocked Package / Other)
**Release manager:**
**Rollback authority (named individual):**
**Rollback alternate (named individual):**

---

## Context Gathered

Answer these before proceeding to classification:

- **Promotion path used:** (list each environment and validation date)
- **Does each sandbox match current production metadata state?** (yes / no — if no, describe delta)
- **Pre-retrieve backup location:** (path or "not yet captured — REQUIRED before window opens")
- **Prior package version (if applicable):**
- **Business impact of a 1-hour outage during this window:**

---

## Risk-Classified Component Inventory

Complete one row per metadata component or component group.

| Component (type: name) | Classification | Risk Indicator | Rollback Asset Available? |
|---|---|---|---|
| (e.g. PermissionSet: Financial_Data_Viewer) | HIGH | Affects FLS on financial object; no feature flag | Pre-retrieve backup: .rollback-backup/2026-04-13 |
| (e.g. Flow: Opportunity_Close_Date_Validation) | HIGH | Bulk-affecting; no prior version gating | Feature flag: Enable_Close_Date_Validation CP |
| (e.g. Layout: Account-Account Layout) | LOW | UI-only; no automation dependency | Not required |

**Overall release risk level:** HIGH / MEDIUM / LOW
*(Highest individual component rating drives the overall level)*

---

## Rollback Plan

### Trigger Conditions

List the exact observable conditions that authorize the rollback call. Each condition must be measurable.

| Trigger | Measurement Source | Threshold |
|---|---|---|
| (e.g. Apex exception on OpportunityTrigger) | Setup > Apex Exception Email | >50 exceptions in 5 minutes |
| (e.g. Integration endpoint latency) | Monitoring dashboard | >10 seconds for 3 consecutive calls |

### Rollback Procedure

**For org-based deployments (Change Set / CLI):**

1. Locate pre-retrieve backup at: _______________
2. Run:
   ```bash
   sf project deploy start \
     --source-dir .rollback-backup/YYYY-MM-DD \
     --target-org production
   ```
3. Estimated execution time: _______________ minutes
4. Post-rollback smoke test: _______________

**For unlocked package deployments:**

1. Prior package version to install: _______________
2. Run:
   ```bash
   sf package install \
     --package <prior-version-id> \
     --target-org production \
     --wait 20
   ```
3. Estimated execution time: _______________ minutes
4. Data side effects to address: _______________
5. Post-rollback smoke test: _______________

### Monitoring Period

**How long will the team monitor after deployment before declaring stable:** _______________ hours/minutes
**Who is on call for the monitoring period:**

---

## Pre-Deployment Checklist (go/no-go gates)

### People
- [ ] Release manager confirmed available for full window and monitoring period
- [ ] Rollback authority (named individual) confirmed available and reachable
- [ ] Rollback alternate confirmed available and reachable
- [ ] Technical executor confirmed available and has deployment access

### Process
- [ ] All components have been classified HIGH / MEDIUM / LOW with documented rationale
- [ ] Rollback trigger conditions are observable and measurable (no subjective language)
- [ ] Rollback procedure is documented with exact commands and estimated time
- [ ] Post-rollback smoke test is defined
- [ ] Any HIGH-risk component without a feature flag has a tested destructive change file prepared

### Technology
- [ ] Pre-retrieve backup captured from production immediately before window (org-based deploys)
- [ ] Prior package version number recorded and accessible (packaged deploys)
- [ ] All sandbox validations completed at current production metadata state
- [ ] No unresolved metadata dependency warnings from the validation run
- [ ] Deployment artifact is the exact package validated — no last-minute additions

---

## Go/No-Go Sign-Off

| Gate | Status | Notes |
|---|---|---|
| People readiness | GO / NO-GO | |
| Process readiness | GO / NO-GO | |
| Technology readiness | GO / NO-GO | |
| **Overall** | **GO / NO-GO** | |

**Release manager sign-off:** _______________
**Date/time:** _______________

---

## Notes

Record any deviations from the standard risk assessment process and the rationale for each deviation.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall