Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-stress-analysis
Advanced architecture stress analysis methodology for designing systems that survive unknown stresses. Load when --residuality flag is used or when designing high-uncertainty, mission-critical systems.
Passed 17 of 22 test cases with the skill, and 10 of 22 without it.
and 6 more in the full report
7 fixed10 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our engineering team wants to evaluate our multi-tenant SaaS microservices architecture for structural vulnerabilities and cascade risks under extreme disruption scenarios. Could you perform a comprehensive stress analysis by generating an incidence matrix of stressors against components, an adjacency matrix showing inter-component connectivity, and a contagion path analysis? Please synthesize these models to highlight single points of failure and recommend specific decoupling patterns or isolation mechanisms to protect critical service pathways.
| Checked | Without skill | With skill |
|---|---|---|
| The response explicitly identifies attractors as emergent system behaviors under stress and residues as surviving capabilities. | Missed | Passed |
| The response generates non-technical stressor scenarios covering business model or regulatory shifts alongside technical failures. | Missed | Passed |
| The response calculates the adjacency matrix coupling ratio as total connections divided by component count (K/N). | Missed | Passed |
The instructions your model reads when the skill loads.
Complexity science-based approach for architectures surviving unknown future stresses. Based on residuality theory by Barry M. O'Reilly (Former Microsoft Chief Architect, PhD Complexity Science).
Core paradigm: "Architectures should be trained, not designed."
Use for: high-uncertainty environments | mission-critical systems | complex socio-technical systems | innovative products | rapidly evolving markets
Skip for: well-understood stable domains | short-lived MVPs | simple few-component systems | resource-constrained environments
Unexpected events challenging operation. Categories: technical (failures, scaling, breaches) | business model (pricing shifts, competitive disruption) | economic (funding, market crashes) | organizational (restructuring, skill gaps) | regulatory (compliance changes) | environmental (infrastructure failures)
Brainstorm extreme and diverse. Goal = discovery, not risk assessment.
Design elements surviving after breakdown. Ask: "What's left when [stressor] hits?"
Example -- e-commerce under payment outage: residue = browsing, cart, wishlist. Lost: checkout, payment. Stress-informed: allow "reserve order, pay later."
States systems naturally tend toward under stress. Differ from designed intent. Discovered through testing, not predicted.
Example -- social media under growth: designed = proportional scaling, actual attractor = read-heavy CDN mode (reads survive, writes queue/fail). Design for this.
Straightforward solution for functional requirements. No speculative resilience. Document as baseline.
Brainstorm 20-50 across all categories. Include extremes. Engage domain experts. Prioritize by impact (not probability).
Walk each stressor with experts. Ask "What actually happens?" Identify emergent behaviors. Recognize cross-stressor patterns.
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.