Skip to content
Back to skills

Stress Scenario

ASecurity

What is the worst case? — Extreme condition construction and failure mode enumeration for risk preparedness

  • 417 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
researchgotesting

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill stress-scenario --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Stress Scenario?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Stress Scenario
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-stress-scenario/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-stress-scenario)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: stress-scenario
description: "What is the worst case? — Extreme condition construction and failure mode enumeration for risk preparedness"
version: 1.0.0
category: experiment-execution
type: strategy
used-by: scenario-planning
sops:
  - scenario-driver-identification
  - worst-case-construction
  - scenario-impact-assessment
  - robustness-scoring
  - scenario-synthesis
tactics:
  - strategy-robustness-testing
---

# Strategy: Stress Scenario

## Methodology

Stress Testing combined with Failure Mode Analysis. Deliberately construct extreme but plausible scenarios that maximally challenge the research approach. Identify breaking points, failure modes, and minimum conditions for viability.

Key principles:
- **Extreme but plausible**: Push parameters to edges without crossing into fantasy
- **Failure-seeking**: Actively look for conditions that break the approach
- **Compound stress**: Combine multiple adverse conditions (correlated failures)
- **Recovery assessment**: For each failure, assess whether recovery is possible

## Execution Flow

1. **Identify drivers** → spawn `scenario-driver-identification`
   - Input: research context, focus on threat vectors
   - Output: vulnerability drivers and failure dimensions

2. **Construct worst cases** → spawn `worst-case-construction` (×3-5)
   - Input: driver extremes, compound combinations
   - Output: extreme scenario descriptions

3. **Assess impact** → spawn `scenario-impact-assessment` (per worst case)
   - Input: stress scenario, research approach
   - Output: failure mode analysis, breaking points

4. **Score robustness** → spawn `robustness-scoring`
   - Input: all stress test results
   - Output: stress robustness index, failure threshold map

5. **Synthesize** → spawn `scenario-synthesis`
   - Input: stress scenarios, failure modes, robustness scores
   - Output: risk report with mitigation recommendations

## Budget Gate

| Step | Token Budget | Notes |
|------|-------------|-------|
| Driver identification | 8K | Threat-focused |
| Worst-case construction | 12K × N | N = 3-5 stress scenarios |
| Impact assessment | 12K × N | Deeper analysis for stress |
| Robustness scoring | 10K | Failure threshold mapping |
| Synthesis | 12K | Risk mitigation report |

Files in this skill

  • SKILL.md2.2 KB
  • prompt.md2.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.