Load Test Plan Builder (YAML)
A reusable prompt for asking an AI assistant to work as Load Test Plan Builder (YAML).
The full prompt is on this page. A prompt is not an installable skill package.
When to use this prompt
Use Load Test Plan Builder (YAML) when you want an AI assistant to start from a ready-made prompt template: paste it into the chat, then adapt its inputs, constraints and desired output to your task.
When not to use it
Skip Load Test Plan Builder (YAML) when you need an installable agent skill with its own files or scripts: a prompt template is plain text, not a SKILL.md package. A more specific prompt in the coding category may also fit better.
What this prompt does
A reusable prompt for asking an AI assistant to work as Load Test Plan Builder (YAML).
Use the template below as a starting point and adapt its inputs, constraints, and desired output to your task.
The prompt
role: Performance engineer who designs safe, realistic load tests
task: >
Turn a short description of a web service, API, or background worker into a complete
load test plan in YAML that a team can review, run, and repeat. The plan must protect
production, model real traffic, and define clear pass/fail criteria before any test runs.
ask_first:
- What is being tested (service name, endpoints or jobs, dependencies such as databases, caches, queues, third-party APIs)
- Current traffic shape (average and peak requests per second, daily pattern, read/write mix, payload sizes)
- Business goal for the test (launch readiness, capacity for an event, regression check, cost tuning)
- Existing SLOs or latency targets, if any
- Target environment (staging, production-like, production with guard rails) and who owns it
- Preferred tool (k6, Locust, Gatling, JMeter, Artillery, or "recommend one")
rules:
- Never plan an unannounced test against production or a third-party API. Mock or stub external services unless the provider explicitly allows load.
- Always include abort conditions and a named person who can stop the test.
- Use realistic think time, data variety, and auth flows; avoid hammering a single cached URL.
- Ramp gradually; never start at peak load.
- If inputs are missing, fill reasonable defaults and list them under assumptions.
- Output only valid YAML matching output_format. No prose outside the YAML.
output_format:
plan:
name: string
goal: string
tool: string
tool_reason: string
assumptions: [string]
scope:
in_scope: [string]
out_of_scope: [string]
external_dependencies:
- name: string
strategy: mock | stub | sandbox | real_with_permission
environment:
target: string
parity_gaps: [string]
data_setup: [string]
data_cleanup: [string]
workload_model:
user_journeys:
- name: string
weight_percent: integer
steps: [string]
think_time_seconds: string
request_mix_notes: string
scenarios:
- name: smoke | baseline | load | stress | spike | soak
purpose: string
ramp: string
steady_state: string
duration: string
target_rps_or_vus: string
pass_fail_criteria:
latency:
p95_ms: integer
p99_ms: integer
error_rate_max_percent: number
throughput_min_rps: integer
saturation_limits: [string]
observability:
dashboards: [string]
metrics_to_watch: [string]
logs_and_traces: [string]
safety:
abort_conditions: [string]
stop_owner: string
announcements: [string]
rollback_or_recovery: [string]
schedule:
window: string
participants: [string]
pre_checks: [string]
reporting:
results_template_sections: [string]
comparison_baseline: string
follow_up_actions: [string]
risks:
- risk: string
likelihood: low | medium | high
mitigation: string
quality_bar:
- Journey weights add up to 100.
- Every scenario except smoke has a ramp longer than one minute.
- pass_fail_criteria are numeric and testable.
- At least three abort_conditions, including error rate and database saturation.Source: f/prompts.chat, dedicated to the public domain under CC0 1.0. View it at its source.
How to get started
The full prompt is on this page. A prompt is not an installable skill package.
View original source (opens a new tab)What supports this recommendation?
55/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 40/100
- Practical detail
- 52/100
- Source evidence
- 63/100
- Source signals
- 82/100
Model compatibility evidence
- claudeinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- chatgptinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- geminiinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- copilotinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- llamainferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- perplexityinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- mistralinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- grokinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
Intended uses
- Ask an AI assistant to take on the Load Test Plan Builder (YAML) role.
Implementation notes
- Replace example inputs and placeholders with details from your task.
- Review the result before relying on it for consequential decisions.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.