Scale Game

Run extreme-scale experiments across volume, speed, users, duration, and failure rate.

3|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/zircote/agents --skill scale-game-zircote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Scale Game
Source: https://github.com/zircote/agents/tree/main/skills/problem-solving/scale-game
Command: npx skills add https://github.com/zircote/agents --skill scale-game-zircote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exposes fundamental scalability truths by forcing deliberate extreme-scale experiments, helping teams identify bottlenecks early and guide robust architectural decisions.

Core Features & Use Cases

  • Define and run extreme-scale tests across dimensions such as volume, speed, users, duration, and failure rate.
  • Capture actionable insights into where performance degrades and which components survive under stress.
  • Share findings to inform architecture, capacity planning, and test strategy.

Quick Start

Select a dimension, push it to an extreme (e.g., 1000x bigger or smaller), and observe what fails and what remains robust.

Frequently Asked Questions about Scale Game

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

FAQPage Schema
What is extreme-scale stress testing in software architecture?

Extreme-scale stress testing forces architecture validation by pushing dimensions like volume, speed, users, duration, and failure rate to limits. It exposes fundamental scalability truths to identify performance bottlenecks early and guide robust design decisions.

How do I perform a scalability stress test to find system limits?

To perform a scalability stress test, select a dimension, push it to an extreme like 1000x bigger or smaller, and observe what fails and what survives. Capture actionable insights on component degradation to inform capacity planning and test strategy.

When do I need to run extreme-scale experiments for QA?

You need to run extreme-scale experiments for QA when validating architecture across dimensions such as volume, speed, users, duration, and failure rate. This process reveals where performance degrades under stress and which components remain robust.

What is the best way to document stress test findings for architecture validation?

The best way to document stress test findings is maintaining a disciplined process with defined steps and notes on failures and survivals. Translate these findings into robust design decisions, capacity planning, and test strategy.

Can I use extreme-scale testing to measure failure rate and duration limits?

Yes, you can use extreme-scale testing to measure failure rate and duration limits. By deliberately forcing extreme-scale experiments across these dimensions, you capture actionable insights into where performance degrades and which components survive under stress.