change-request
Create a change management request with impact analysis and rollback plan
What this skill does
# /operations:change-request > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Create a structured change request with impact analysis, risk assessment, and rollback plan. See the **change-management** skill for the assess-plan-execute-sustain framework and communication principles. ## Usage ``` /operations:change-request $ARGUMENTS ``` ## Output ```markdown ## Change Request: [Title] **Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical/High/Medium/Low] **Status:** Draft | Pending Approval | Approved | In Progress | Complete ### Description [What is changing and why] ### Business Justification [Why this change is needed — cost savings, compliance, efficiency, risk reduction] ### Impact Analysis | Area | Impact | Details | |------|--------|---------| | Users | [High/Med/Low/None] | [Who is affected and how] | | Systems | [High/Med/Low/None] | [What systems are affected] | | Processes | [High/Med/Low/None] | [What workflows change] | | Cost | [High/Med/Low/None] | [Budget impact] | ### Risk Assessment | Risk | Likelihood | Impact | Mitigation | |------|-----------|--------|------------| | [Risk] | [H/M/L] | [H/M/L] | [How to mitigate] | ### Implementation Plan | Step | Owner | Timeline | Dependencies | |------|-------|----------|--------------| | [Step] | [Person] | [Date] | [What it depends on] | ### Communication Plan | Audience | Message | Channel | Timing | |----------|---------|---------|--------| | [Who] | [What to tell them] | [How] | [When] | ### Rollback Plan [Step-by-step plan to reverse the change if needed] - Trigger: [When to roll back] - Steps: [How to roll back] - Verification: [How to confirm rollback worked] ### Approvals Required | Approver | Role | Status | |----------|------|--------| | [Name] | [Role] | Pending | ``` ## If Connectors Available If **~~ITSM** is connected: - Create the change request ticket automatically - Pull change advisory board schedule and approval workflows If **~~project tracker** is connected: - Link to related implementation tasks and dependencies - Track change progress against milestones If **~~chat** is connected: - Draft stakeholder notifications for the communication plan - Post change updates to the relevant team channels ## Tips 1. **Be specific about impact** — "Everyone" is not an impact assessment. "200 users in the billing team" is. 2. **Always have a rollback plan** — Even if you're confident, plan for failure. 3. **Communicate early** — Surprises create resistance. Previews create buy-in.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.