slo-load-test-plan

Produces one artifact: a load-test plan in which every scenario has a name, a load shape, an injection model, and a pass/fail line traceable to a stated SLO.

What this skill owns, and what it does not

Owned here	Owned elsewhere
Which scenarios exist, and why each one exists	Nothing
The load shape each scenario applies (profile, ramp, plateau, injection model)	Nothing
The pass/fail line each scenario carries, expressed as a threshold derived from an SLO	Nothing
The error budget each threshold is sized against	Nothing
Runner-specific configuration: executor blocks, protocol setup, feeders, distributed workers, result stores	A per-tool wrapper for k6, Gatling, JMeter, or Locust
Aggregating verdicts from several runners into one CI go / no-go	A multi-runner CI gate
Finding which commit caused a regression after the plan is already running	A bisection workflow