tda-scenario-stress-test

Stress-test strategic research decisions across six risk branches before committing to a task brief.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill tda-scenario-stress-test-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tda-scenario-stress-test
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/tda-scenario-stress-test
Command: npx skills add https://github.com/ZK-Theory/TDL --skill tda-scenario-stress-test-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research programmes face strategic choices — paper structure, robustness checks, baselines, methods trade-offs — where committing too early leads to reviewer objections, scope creep, or costly rework. This Skill runs structured pre-decision risk analysis so each option is examined from best, worst, and reviewer-hostile angles before it becomes a task brief. ## Core Features & Use Cases - Six-branch scenario analysis: Evaluates every option across best case, likely case, worst case, reviewer-hostile case, maintenance-cost case, and paper-scope-risk case. - Lock enforcement: Detects options foreclosed by locked conventions, contracts, or pre-registrations and removes them instead of reopening settled decisions. - Actionable output record: Produces a recommendation with named residual risks and a defined next step — a task brief, a user decision point, or dropping the option. - Use Case: When deciding whether a methods paper should include a conventional baseline, run the six branches to surface the reviewer-hostile objection ("why wasn't this pre-registered?") and scope-leak risks, then convert the surviving recommendation into a task brief. ## Quick Start Ask the assistant to stress-test a research decision such as whether to add a robustness check to a paper, and request the six-branch analysis with a recommendation.

Frequently Asked Questions about tda-scenario-stress-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a research decision before committing to it?

State the decision as a single question with enumerated options, then run six branches per option: best, likely, worst, reviewer-hostile, maintenance-cost, and paper-scope-risk cases. Weigh the branches and convert the recommendation into a task brief or user decision point.

What risk scenarios should I analyze before changing a paper's structure?

Analyze best case, likely case, worst case, reviewer-hostile objections such as cherry-picking or missing pre-registration, maintenance costs for scripts and figures, and paper-scope risks like applied interpretation leaking into methods sections.

When should I not use scenario stress testing for a decision?

Do not use it when the decision is already constrained by a locked convention, contract, or pre-registration. Reopening a locked decision is a user decision requiring a [DECISION] entry, not a scenario exercise.

How is pre-decision stress testing different from design review?

Scenario stress testing runs upstream before a choice is committed, analyzing plausible branches of a decision. Adversarial design review attacks an existing artifact at a review gate after it has been produced.

What does the output of a scenario stress test contain?

The output record contains the decision question, options with any foreclosed by locks, six branches per surviving option, a recommendation, named residual risks, and the next step: task brief, user decision, or drop.