> ## Documentation Index
> Fetch the complete documentation index at: https://closedloop.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Bug Blast Radius

> Answer how important a bug is: who reported it, how badly, what those customers are worth, and whether it is still happening today.

You have a defect and a sprint that is already full. This skill answers the one question that decides the ordering: how important is this bug? It reports who reported it, how severe they said it was, what those customers are worth, and whether it is still being reported.

## Usage

```
/closedloop-bug-blast-radius how bad is the saved-card checkout failure?
/closedloop-bug-blast-radius is the CSV export timeout worth fixing this sprint?
/closedloop-bug-blast-radius blast radius for the SSO redirect loop
```

One defect at a time, in your own words. Name a feature area or a date window to narrow it. Say it is an integration or sync problem and the search widens to include integration issues, which sit outside the default set.

## What You Get

* **An exposure score out of 100**, with the categories that were searched printed beside it
* **Customer count and insight count**: how many customers reported this, and how many separate reports they filed
* **Revenue**: the ARR of the customers who reported it, in your CRM's own currency
* **Trend**: accelerating, steady, or gone quiet, with the date it was last reported
* **A recommendation**: hotfix, next sprint, or backlog, with the rule that fired and the numbers that satisfied it
* **Per-customer rows**: name, ARR, report count, deal-blocker and churn state, and a verbatim quote
* **Excluded customers**: the ones whose evidence turned out to be a different problem, named with the reason
* **Coverage caveats**: what the numbers can and cannot support

## Recommendation Rules

The thresholds print on every run, so you can disagree with the rule rather than the number.

| Recommendation | Rule                                                                                |
| -------------- | ----------------------------------------------------------------------------------- |
| Hotfix         | Any deal blocker, or any Critical, still reported within 30 days                    |
| Next sprint    | Exposure score at or above 50, or an accelerating trend with more than one customer |
| Backlog        | Everything else                                                                     |

## Design Principles

**Reported, never affected.** Customers who hit the bug and never contacted you are not in these numbers, and the skill says so on every run.

**Read the evidence before reporting it.** Semantic retrieval pulls in adjacent complaints: a different bug in the same area, a feature request phrased as a failure, a duplicate of something already fixed. The skill reads every returned insight, names the ones that are a different problem, and gives you both the raw and the corrected number.

**Zero revenue is not zero impact.** When no priced deals resolve for the reporting customers, that is what it says, rather than "no revenue at risk".

**Never says a bug is fixed.** It gives you the last reported date and lets you conclude.

**Read only.** No writes, no notifications, no other tools.