SkillVaultskills Browse all 500 skills

Reliability · Version 1.2.0 · Reviewed 2026-08-02

Dependency Failure Drill Designer

Reduce production risk in drill scoping and safety controls with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Designs safe exercises that verify fallback behavior by actually failing a dependency.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Drill scoping
  • Safety controls
  • Result interpretation

How Dependency Failure Drill Designer works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind drill scoping

It decides

A safety controls plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Dependency Failure Drill Designer designs safe exercises that verify fallback behavior by actually failing a dependency. Use it when the work involves Drill scoping, Safety controls, Result interpretation.

  1. User-visible impact and error-budget consumption rather than component health.
  2. Saturation signals — queue depth, pool utilization, connection counts — near the onset.
  3. Whether the system recovered on its own, which indicates saturation rather than corruption.
  4. The blast radius and what boundary should have contained it.

Failure modes it recognizes

  • Retry amplification turning a partial failure into a total outage.
  • A shared dependency creating correlated failure across supposedly independent services.
  • Slow resource exhaustion invisible until a hard limit is crossed.
  • A rollback blocked by an incompatible migration.

Answers it will reject

  • Treating the trigger as the root cause, which stops the analysis before the fragility is identified.
  • Adding a runbook step where a boundary would remove the failure mode.
  • Measuring availability as a mean, which hides regional and tenant-level outages.

Decision rules it applies

  • Stabilize user impact before completing diagnosis.
  • Bound every retry with a budget, jitter, and a circuit breaker.
  • Prefer removing a failure mode over detecting it faster.

Evidence it asks for

  • Record time-to-detect, time-to-mitigate, and time-to-resolve separately.
  • Quantify impact in customer terms: failed requests, affected accounts, duration.
  • Verify recovery with the same signal that detected the failure.

The method inside

  1. Turn drill scoping into explicit functional requirements and quality-attribute constraints.
  2. Model the critical path, state, trust, and failure boundaries that govern safety controls.
  3. Compare viable designs for result interpretation against weighted constraints and operational ownership.
  4. Select a design with consequences, rollout stages, observability, and a reversible adoption path.

Deliverables

  • Drill scoping assessment
  • Safety controls decision and action plan
  • Result interpretation verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We believe our fallbacks work but have never tested them. How do we verify without risking customers?

Expected output

Belief in an untested fallback is the thing worth removing. Start in staging with production-like traffic, then run a bounded production drill on a small traffic slice with an automatic abort, and treat a fallback that fails as an incident with a postmortem...

Boundaries and compatibility

Ideal for

  • Drill scoping: produce a decision or artifact grounded in supplied evidence.
  • Safety controls: produce a decision or artifact grounded in supplied evidence.
  • Result interpretation: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.