SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.2.0 · Reviewed 2026-08-02

Release Risk Assessment Combiner

Reduce production risk in release risk aggregation and risk dimension reconciliation with evidence, explicit trade-offs, and a verification plan.

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

Combines independent functional, security, deployment, observability, test, and recovery assessments into one calibrated release view. It grounds the decision in dimension findings, confidence, severity scales, dependencies, release criteria, and override policy and explicitly prevents averaging away one release-blocking risk or double-counting correlated findings from multiple reviewers.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Release risk aggregation
  • Risk dimension reconciliation
  • Release blocker override

How Release Risk Assessment Combiner works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind release risk aggregation

It decides

A risk dimension reconciliation plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Release Risk Assessment Combiner combines independent functional, security, deployment, observability, test, and recovery assessments into one calibrated release view. It grounds the decision in dimension findings, confidence, severity scales, dependencies, release criteria, and override policy and explicitly prevents averaging away one release-blocking risk or double-counting correlated findings from multiple reviewers. Use it when the work involves Release risk aggregation, Risk dimension reconciliation, Release blocker override.

  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. Establish what is actually true about release risk aggregation from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind risk dimension reconciliation rather than restating the symptom.
  3. Choose the smallest defensible change for release blocker override, weighing impact, confidence, effort, and reversibility.
  4. Define measurable ownership and verification

Deliverables

  • Release risk aggregation assessment
  • Risk dimension reconciliation decision and action plan
  • Release blocker override 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

Apply the release risk assessment combiner to our current release risk aggregation work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with dimension findings, confidence, severity scales, dependencies, release criteria, and override policy. The highest-risk failure is averaging away one release-blocking risk or double-counting correlated findings from multiple reviewers. Preserve blocker overrides, normalize confidence, and combine correlated mechanisms once with traceable component scores. Verify the result by recalculating known cases by hand and testing missing, conflicting, and not-applicable dimension inputs.

Boundaries and compatibility

Ideal for

  • Release risk aggregation: produce a decision or artifact grounded in supplied evidence.
  • Risk dimension reconciliation: produce a decision or artifact grounded in supplied evidence.
  • Release blocker override: 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 Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

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.