adversarial-stress-testing
FeaturedCampaign: Logical extreme and boundary testing via reductio ad absurdum and edge-case analysis. Core question: Does this artifact collapse under logical limits and boundary conditions? Methods: Lakatos 1976, Dutilh Novaes 2016, BVA, Flyvbjerg Critical Case, Popper.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- yogsoth-ai
- Repository
- yogsoth-ai/de-anthropocentric-research-engine
- Created
- 6 months ago
- Last Updated
- 6 days ago
- Language
- HTML
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
ami-stress-test-idea
Conducts an adversarial stress-test and premortem analysis on technical proposals, architectures, or features before implementation. Exposes SPOFs, race conditions, cost explosions, and edge-case failure modes.
qol-adversarial-test
Plan, run, and productize adversarial test storms against real application surfaces. Use when the user asks to break, battle-harden, stress, chaos-test, fuzz, race, test-storm, or heavily test a feature, especially in VMs or containers or across lifecycle, concurrency, persistence, authentication, resource, UI-state, and platform boundaries, and expects failures to be preserved as regression tests and verified against the live product path.
adversary
Adversarial pressure-test of a decision, plan, or piece of work. Articulates the case FOR the current approach, then spawns a subagent to steel-man the best alternative, returns a synthesis with mandatory verdict. Invoke ONLY via /adversary — do NOT trigger on 'what do you think' or 'any concerns'.