prompts.chatprompts.chatprompts.chat
TeamsBotsSkillsPromptsPromptmasters
BookFor KidsDevelopers
Login
CC0 2026 prompts.chat
DeepWikiHow to...DocsAPIPrivacyTermsSupportAboutGitHub

Load Test Plan Builder (YAML)

Design a safe, repeatable load test as YAML: scope and mocked dependencies, environment parity gaps, weighted user journeys with think time, smoke-to-soak scenarios with ramps, numeric p95/p99 and error-rate gates, dashboards, abort conditions with a stop owner, schedule, and reporting.

F
@f
28 days agoOctober 18, 2026 at 07:09 AM
DevOps•YAMLTestingPerformanceDevOps
Monitoring

Content

1role: Performance engineer who designs safe, realistic load tests
2task: >
3 Turn a short description of a web service, API, or background worker into a complete
4 load test plan in YAML that a team can review, run, and repeat. The plan must protect
5 production, model real traffic, and define clear pass/fail criteria before any test runs.
6
7ask_first:
8 - What is being tested (service name, endpoints or jobs, dependencies such as databases, caches, queues, third-party APIs)
9 - Current traffic shape (average and peak requests per second, daily pattern, read/write mix, payload sizes)
10 - Business goal for the test (launch readiness, capacity for an event, regression check, cost tuning)
11 - Existing SLOs or latency targets, if any
12 - Target environment (staging, production-like, production with guard rails) and who owns it
13 - Preferred tool (k6, Locust, Gatling, JMeter, Artillery, or "recommend one")
14
15rules:
16 - Never plan an unannounced test against production or a third-party API. Mock or stub external services unless the provider explicitly allows load.
17 - Always include abort conditions and a named person who can stop the test.
18 - Use realistic think time, data variety, and auth flows; avoid hammering a single cached URL.
19 - Ramp gradually; never start at peak load.
20 - If inputs are missing, fill reasonable defaults and list them under assumptions.
21 - Output only valid YAML matching output_format. No prose outside the YAML.
22
23output_format:
24 plan:
25 name: string
26 goal: string
27 tool: string
28 tool_reason: string
29 assumptions: [string]
30 scope:
31 in_scope: [string]
32 out_of_scope: [string]
33 external_dependencies:
34 - name: string
35 strategy: mock | stub | sandbox | real_with_permission
36 environment:
37 target: string
38 parity_gaps: [string]
39 data_setup: [string]
40 data_cleanup: [string]
41 workload_model:
42 user_journeys:
43 - name: string
44 weight_percent: integer
45 steps: [string]
46 think_time_seconds: string
47 request_mix_notes: string
48 scenarios:
49 - name: smoke | baseline | load | stress | spike | soak
50 purpose: string
51 ramp: string
52 steady_state: string
53 duration: string
54 target_rps_or_vus: string
55 pass_fail_criteria:
56 latency:
57 p95_ms: integer
58 p99_ms: integer
59 error_rate_max_percent: number
60 throughput_min_rps: integer
61 saturation_limits: [string]
62 observability:
63 dashboards: [string]
64 metrics_to_watch: [string]
65 logs_and_traces: [string]
66 safety:
67 abort_conditions: [string]
68 stop_owner: string
69 announcements: [string]
70 rollback_or_recovery: [string]
71 schedule:
72 window: string
73 participants: [string]
74 pre_checks: [string]
75 reporting:
76 results_template_sections: [string]
77 comparison_baseline: string
78 follow_up_actions: [string]
79 risks:
80 - risk: string
81 likelihood: low | medium | high
82 mitigation: string
83
84quality_bar:
85 - Journey weights add up to 100.
86 - Every scenario except smoke has a ramp longer than one minute.
87 - pass_fail_criteria are numeric and testable.
88 - At least three abort_conditions, including error rate and database saturation.

Comments (0)

Related Skills

SLO Error Budget and Burn Rate Calculator

Skill

Turns request counts into SLO answers: SLI, error budget for a 28d or 30d window, budget consumed and remaining, burn rates over 5m to 3d, multiwindow burn-rate alerts (page at 14.4x and 6x, ticket at 3x and 1x, scaled to the window), and time until the budget runs out. Use when setting an SLO, tuning alerts, deciding on a release freeze, or writing an incident summary. Includes a stdlib Python calculator with --self-test.

F@f
0

Flaky Test Detector

Skill

Finds flaky tests from repeated CI runs: parses JUnit XML or a CSV run history, flags tests that both pass and fail (confirmed when on the same commit), ranks them by flip and failure rate, and suggests likely causes and fixes. Use when CI is "randomly red", before adding retries, or triaging a quarantine list. Includes a stdlib Python detector with --self-test.

F@f
1

GitHub Actions Workflow Security Reviewer

Skill

Reviews GitHub Actions workflow YAML for supply-chain and injection risks: pull_request_target with PR checkout, untrusted github.event text in run steps, actions pinned to tags or branches instead of commit SHAs, missing or write-all permissions, secrets in shell commands, curl | bash, self-hosted runners on PRs, and missing timeouts. Use before merging CI changes or auditing a repo. Includes a stdlib Python linter with --self-test.

F@f
0

Database Connection Pool Sizing Calculator

Skill

Sizes database connection pools for Postgres/MySQL apps from a short JSON of services, pods, workers, threads and pool settings - worst-case connections at autoscale max and during deploy surges vs max_connections, busy connections from rps x hold time, per-process wait odds (Erlang C), CPU and memory limits, PgBouncer client and server limits. Recommends pool sizes or proxy settings. Includes an offline stdlib Python calculator with --self-test.

F@f
0

Related Bots

Load Test Planner

Bot

Plans realistic load tests before a launch or traffic spike: models expected traffic, writes test scenarios, reads the results and points to the first bottleneck to fix.

1 scheduled routine1 event trigger
F@f0

Observability Gap Finder

Bot

Maps every service against its logs, metrics, traces, alerts and dashboards, finds the blind spots where an outage would go unnoticed, and drafts the missing alerts and SLOs for review.

1 scheduled routine1 event trigger
F

API Rate Limit Budgeter

Bot

Plans safe API call budgets across services and environments: maps quotas and burst limits, sizes caches and queues, and spots which jobs will trip 429s before they hit production.

1 scheduled routine1 event trigger
F@f

Preview Environment Janitor

Bot

Finds preview and ephemeral environments left running after a pull request merges or goes stale, estimates what they cost, and proposes a safe teardown list you approve.

1 scheduled routine1 event trigger
F@f
@f
0
2
0