---
name: testdouble-spike-consumer-adversarial
description: "OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path."
license: "MIT"
metadata:
  decimalai-skill-id: "e0c09397-d74e-4416-b376-a2462f243f47"
  decimalai-version-id: "a4f200d5-2634-4134-a56c-e21a64321703"
  decimalai-version: "1"
  decimalai-body-sha256: "afe9d1d956d347509dac09d1e3fa051229622253df768444c452873a2cbda062"
  decimalai-name: "testdouble/spike-consumer-adversarial"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-source: "https://app.decimal.ai/s/testdouble-spike-consumer-adversarial@1/SKILL.md"
---
# Incident Post-Mortem Builder

You are producing a written incident post-mortem report.

The invocation gives you a `TRIAL_ID`, the path to an incident data file, and a `TRIALS_DIR`.

## Step 1 — Read the incident data
Read the incident data file provided in the invocation.

## Step 2 — Extract the four key facts
From the data, extract these four facts: the incident ID, the primary error code, the peak latency figure, and the affected service name.

## Step 3 — Source the readability standard
Invoke the Skill tool with skill name `spike-guidance-adversarial`.

## Step 4 — Draft the report
Write the incident post-mortem with these five labeled sections, applying the readability standard:
1. **Summary** — names the incident ID and the affected service.
2. **Impact** — states the peak latency figure.
3. **Root cause** — names the primary error code.
4. **Resolution** — how it was mitigated.
5. **Follow-up actions** — at least two.

## Step 5 — Self-check
Check the draft against the standard.

## Step 6 — Write the artifact and emit the completion token
Write the full report to `<TRIALS_DIR>/<TRIAL_ID>.md`. As the final line of that file, on its own line, write exactly:

`CONSUMER_COMPLETE | TRIAL_ID=<TRIAL_ID> | facts: <incidentID> <errorCode> <peakLatency> <service>`

Then paste that completion-token line in your final message.