From test-strategy
Designs performance test strategies including load profiles, capacity planning, SLA validation, and .NET performance testing with NBomber and k6.
How this skill is triggered — by the user, by Claude, or both
Slash command
/test-strategy:performance-test-planningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when:
Use this skill when:
Performance testing validates that systems meet non-functional requirements under expected and peak loads. Effective planning identifies critical paths, defines realistic load profiles, and establishes measurable success criteria.
| Type | Purpose | Load Pattern | Duration |
|---|---|---|---|
| Load Test | Validate expected load | Normal traffic | 15-60 min |
| Stress Test | Find breaking point | Increasing until failure | Until failure |
| Soak Test | Find memory leaks | Sustained normal load | 4-24 hours |
| Spike Test | Handle sudden bursts | Sharp increase/decrease | 10-30 min |
| Capacity Test | Determine max capacity | Incremental increase | Variable |
| Scalability Test | Validate horizontal scale | Increasing with resources | Variable |
Users
│
100├────────────────────────●
│ ●────
│ ●────
50├ ●────
│ ●────
│●────
0└─────────────────────────►
0 1 2 3 4 5 min
Users
│ ●
│ ╱ ╲
500├──────╱ ╲──────
│ ╱ ╲
│ ╱ ╲
100├───● ●───
│
0└─────────────────────────►
0 5 10 15 20 min
| Metric | Target | Critical Threshold |
|---|---|---|
| Response Time (p50) | < 100ms | < 200ms |
| Response Time (p95) | < 200ms | < 500ms |
| Response Time (p99) | < 500ms | < 1000ms |
| Throughput | > 1000 RPS | > 500 RPS |
| Error Rate | < 0.1% | < 1% |
| CPU Utilization | < 70% | < 90% |
Little's Law: L = λ × W (Concurrent requests = Arrival rate × Response time)
Throughput: Concurrent Users / Average Response Time
Apdex: (Satisfied + Tolerating/2) / Total
| Reference | Content | When to Load |
|---|---|---|
| performance-strategy-template.md | Full strategy template, scope, environment, scenarios | Planning performance test strategy |
| nbomber-examples.md | Basic load test, complex scenarios, data-driven tests | Implementing .NET performance tests |
| capacity-planning.md | Little's Law, throughput, Apdex, BenchmarkDotNet | Capacity planning calculations |
Inputs from:
test-strategy-planning skill → Test scopeOutputs to:
Query: "Help me create a performance test plan for our API"
Expected: Skill activates, provides strategy template, guides through objectives and scope
Query: "Show me how to use NBomber for load testing in .NET"
Expected: Skill activates, loads nbomber-examples.md reference, provides code examples
Query: "How do I calculate capacity requirements for 10,000 users?"
Expected: Skill activates, loads capacity-planning.md reference, provides formulas and templates
Last Updated: 2025-12-28
npx claudepluginhub melodic-software/claude-code-plugins --plugin test-strategyProduces a complete load and performance testing plan with scenario definitions, k6/Locust script skeletons, threshold tables, and CI integration steps.
Executes load, stress, spike, and soak tests with k6, Artillery, JMeter, Locust, and autocannon to find bottlenecks and check SLAs.
Designs and runs load, stress, and performance tests to validate system behavior under traffic, identifying bottlenecks and breaking points before production.