LT
Load Testing Plan
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Write a load and performance testing plan for a service. Use when asked to create a performance test plan, write load testing documentation, define stress or soak test scenarios, or set performance regression gates for CI. Produces a complete test plan document with scenario definitions, k6/Locust script skeleton, threshold table, result interpretation guide, and CI integration steps.
What to give it
▸Service name and key endpoints — which endpoints are under test (path, method, typical request/response shape)
▸Current traffic baseline — current requests/sec, p50/p99 latency, error rate under normal load
▸Peak traffic expectations — expected peak RPS (e.g. 10× baseline for flash sales, or seasonality peak)
▸SLO targets — latency SLOs (p99 < X ms), error rate SLO (< Y%), availability target
▸Preferred testing tool — k6, Locust, JMeter, Gatling, or no preference
▸Test environment availability — dedicated load test environment, staging, or production (with traffic shaping)
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓All key endpoints are covered by at least one test scenario — no production endpoint is untested
✓Thresholds are derived from actual SLO targets, not guesses
✓Test data seeding is scripted and reproducible — tests do not rely on pre-existing environment state
✓The load generator runs on separate infrastructure from the service under test
✓CI integration blocks promotion on threshold failure — not just records results
✓Soak test has been run at least once to establish a memory and connection pool baseline
✓Results comparison to previous run is part of the analysis — not just absolute pass/fail
⚠️ What it refuses to do
Do not set thresholds without grounding them in actual SLO targets or production baselines — arbitrary numbers produce meaningless pass/fail results
Do not run the load generator on the same host as the service under test — this contaminates both the test results and the service metrics
Do not use production user data in load test seeding — all test data must be synthetic, tagged, and cleaned up after each run
Do not skip the soak test on first deployment — only a soak test reveals slow memory leaks and connection pool exhaustion that short tests miss
Do not treat a passing baseline test as evidence the service handles spikes — baseline, stress, spike, and soak scenarios test fundamentally different failure modes
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="load-testing-plan"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Load Testing Plan is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog