Operational Resilience Dependency Mapper

This skill addresses the critical visibility gap between business services and the technical infrastructure supporting them. It stops teams from relying on fragmented notes or vague vendor SLAs that don't reflect actual recovery capabilities. By mapping the full path from customer outcome to the underlying people, data, and third-party dependencies, it exposes single points of failure and recovery-objective mismatches.

What it does

• Map dependency chains by decomposing business services into stages involving people, apps, infra, and fourth-party vendors.
• Identify single points of failure through common-mode analysis of shared hosting, credentials, and geographic concentrations.
• Audit recovery objectives by comparing business impact tolerances against technical RTO/RPO and supplier commitments.
• Triage operational exposure using a transparent scoring heuristic based on consequence, likelihood, and fallback weakness.
• Generate action plans that assign owners to specific gaps, interim controls, and required verification evidence.

How it works

1. Scope definition identifies the service boundary, peak periods, and supplied evidence sources.
2. Decomposition maps the trigger-to-outcome flow across multiple dependency layers.
3. Register normalization creates an auditable table of components with ownership and fallback status.
4. Gap analysis flags discrepancies between stated recovery goals and demonstrated test results.

Frameworks & tools

This tool works with internal business impact assessments (BIA), service level agreements (SLA), configuration management databases (CMDB), and continuity plans. It outputs structured Markdown reports and tables compatible with documentation hubs like Confluence or GitHub.

Why this beats prompting it yourself

Standard prompting often ignores "soft" dependencies like identity services, staff skills, or power. This skill enforces a 12-step QA workflow that prevents the common mistake of equating an application list with a true operational resilience map.

Use cases

• Service mapping for preparing internal triage or management assurance reports.
• Supplier reviews to analyze how vendor dependencies impact critical service delivery.
• Exercise preparation for creating evidence-based scenarios for tabletop or recovery tests.
• Dependency auditing to find inconsistencies in existing continuity documentation.

Known limitations

This is a planning tool, not proof of restoration. It does not access live production systems or certify regulatory compliance. Recovery limits and ownership must be user-supplied.