Get your Teamwork.com risk register back in shape

**Objective:** Audit the open risks in Teamwork for the project matching {project-name} (every project when blank), treating a risk as stale when it has not changed in {stale-days} days (default 30 when blank).

**Step 1: Resolve the scope**

When {project-name} is given, call `teamwork-get-projects` with `name.contains` set to it. If more than one project matches, list them and stop. Keep the `project-id`.

**Step 2: Pull the open risks**

Call `teamwork-get-risks` with `status` set to open, `max-records` 200, and `project-id` when scoped.

**Step 3: Flag each risk**

* **No mitigation:** `mitigation-plan` is empty.
* **Stale:** `last-changed-on` (or `created-on` when that is empty) is older than the stale threshold.
* **Severe:** among the highest quarter of `result` scores returned, or both `impact-value` and `probability-value` at the top of the range returned.

A severe risk with no mitigation is the most important finding. Put those first.

**Step 4: Look for missing risks**

Call `teamwork-get-project-updates` with `is-active` set to true and `health-label` set to bad (add `project-id` when scoped). Any project with a bad health label and no open risk is a gap in the register.

**Step 5: Report**

* Counts: open risks, severe, no mitigation, stale.
* A table sorted severe-and-unmitigated first: project, `source`, impact, probability, result, flags, `created-by`, `last-changed-on`, `risk-id`.
* Projects rated bad with no open risks.
* Up to three recommendations, each naming the risks or projects it applies to.

**Rules & Guidelines:**

* This prompt is read-only. Do not call any tool whose name begins with teamwork-create-, teamwork-update-, teamwork-complete-, teamwork-uncomplete-, teamwork-assign-, teamwork-move-, teamwork-copy-, teamwork-clone-, teamwork-reorder-, teamwork-archive-, teamwork-unarchive-, teamwork-lock- or teamwork-unlock-, and do not call `teamwork-get-file-shared-link`.
* In particular, do not call `teamwork-create-risk` or `teamwork-update-risk`, even for an obvious gap. Recommend it instead.

**Validation:**

* When there are no open risks, say so, and still run Step 4.
* When {stale-days} is not a whole number, use 30 and say so.