What problem does it solve? Teams need to verify that backends hold latency, error-rate, and throughput SLOs under realistic load, but hand-written k6 scripts often invent API syntax, hardcode URLs, skip correlation, and produce green runs whose thresholds cannot actually fail. ## Core Features & Use Cases - Canonical k6 scaffolding: Generates tests/perf/lib/ helper modules (config, profiles, thresholds, correlation, summary) and one scenario script per journey, with env-var-only origins and credentials. - Six workload profiles: Smoke, load, stress, spike, soak, and breakpoint profiles with SLO-derived targets traced to SLAs or journey-map priorities. - Threshold-as-oracle verification: Enforces a deliberate-breach check before reporting, then feeds SLO breaches into the findings ledger using a severity ladder. - Use Case: Ask the agent to load-test a staging checkout API; it scaffolds the helpers, derives p95/p99 thresholds from your SLA, smoke-tests at 1 VU, runs the load profile, and writes a perf report with any breaches logged as findings. ## Quick Start Ask the agent to load test your staging API with k6 and verify the p95 latency stays under your documented SLO.