disruption-response-coordinator
Supply chain disruption rapid response skill with impact assessment and mitigation activation
What this skill does
# Disruption Response Coordinator
## Overview
The Disruption Response Coordinator manages rapid response to supply chain disruptions. It provides structured incident classification, impact assessment, mitigation activation, stakeholder communication, and recovery tracking to minimize disruption impact.
## Capabilities
- **Incident Classification and Escalation**: Severity-based incident categorization
- **Impact Assessment**: Supply, demand, and financial impact analysis
- **War Room Coordination**: Cross-functional response team orchestration
- **Mitigation Option Activation**: Contingency plan execution
- **Stakeholder Communication**: Internal and external communication management
- **Recovery Tracking**: Progress monitoring toward normal operations
- **Lessons Learned Capture**: Post-incident documentation
- **Post-Incident Analysis**: Root cause and improvement identification
## Input Schema
```yaml
disruption_response_request:
incident:
incident_id: string
type: string # supplier, logistics, demand, natural disaster
description: string
affected_entities: array
detection_time: datetime
reported_by: string
initial_assessment:
estimated_duration: string
affected_products: array
affected_customers: array
financial_exposure: float
available_mitigations:
alternative_suppliers: array
buffer_inventory: object
demand_management: array
communication_requirements:
internal_stakeholders: array
external_stakeholders: array
regulatory_notifications: array
```
## Output Schema
```yaml
disruption_response_output:
incident_classification:
severity: string # Minor, Moderate, Major, Critical
escalation_level: string
incident_commander: string
impact_assessment:
supply_impact:
affected_skus: array
shortage_forecast: object
demand_impact:
affected_customers: array
revenue_at_risk: float
financial_impact:
total_exposure: float
breakdown: object
response_plan:
activated_mitigations: array
action_items: array
- action: string
owner: string
due_date: datetime
status: string
war_room_schedule: object
communication_log:
internal_updates: array
external_communications: array
regulatory_notifications: array
recovery_tracking:
current_status: string
milestones: array
estimated_recovery_date: date
progress_percentage: float
lessons_learned:
root_cause: string
what_worked: array
improvement_opportunities: array
action_items: array
```
## Usage
### Incident Classification
```
Input: Disruption event details, affected scope
Process: Classify severity, determine escalation
Output: Incident classification with response level
```
### Impact Assessment
```
Input: Affected suppliers/products, demand data
Process: Model supply shortage, customer impact
Output: Quantified impact assessment
```
### Mitigation Activation
```
Input: Available alternatives, contingency plans
Process: Select and activate appropriate mitigations
Output: Active mitigation plan with assignments
```
## Integration Points
- **Incident Management Systems**: Ticketing, escalation
- **Communication Platforms**: Notification, collaboration
- **Supply Chain Systems**: Inventory, order management
- **Tools/Libraries**: Incident management, communication tools
## Process Dependencies
- Supply Chain Disruption Response
- Business Continuity and Contingency Planning
- Supplier Risk Monitoring and Early Warning
## Best Practices
1. Establish clear severity criteria upfront
2. Pre-define escalation paths and thresholds
3. Maintain updated contact lists
4. Practice response through simulations
5. Communicate early and often during incidents
6. Conduct thorough post-incident reviews
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.