performance-slo-planner

Generates SLI, SLO, load model, and test matrix plans for production readiness.

1.4k|284|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/microsoft/hve-core --skill performance-slo-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-slo-planner
Source: https://github.com/microsoft/hve-core/tree/main/.github/skills/project-planning/performance-slo-planner
Command: npx skills add https://github.com/microsoft/hve-core --skill performance-slo-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often enter production with vague expectations like "it should be fast and reliable" but no measurable targets. This Skill turns those expectations into concrete SLIs, SLOs, error budgets, load models, and a reliability backlog that can be reviewed and executed.

Core Features & Use Cases

  • SLO and Error Budget Definition: Derives measurable SLIs (latency p50/p95/p99, availability, error rate, false-positive rate) with targets, windows, and error budgets anchored to PRD NFR ids.
  • Load Modeling and Test Matrix: Defines steady, peak, spike, and soak profiles and maps them to critical user journeys with pass/fail thresholds for Azure Load Testing execution.
  • Reliability Backlog and Observability Hooks: Produces a prioritized SRE backlog and names the metrics and traces needed to measure each SLI in production.
  • Use Case: Before launching an incident-response app, use this Skill to convert PRD NFRs like "Critical ≤ 60s" into a full performance plan with load profiles, capacity assumptions, and degradation behavior.

Quick Start

Ask the agent to create a performance and SLO plan for your application using its critical user journeys and traffic assumptions.

Frequently Asked Questions about performance-slo-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define SLOs and error budgets for a new service?

Identify measurable SLIs for each critical user journey, such as p95 latency, availability, and error rate, then set a target and measurement window for each. The error budget follows from the gap between the target and 100 percent.

How to create a load testing plan before production launch?

Define steady-state, peak, spike, and soak load profiles with concurrency, rate, and duration, then map each profile to the user journeys it exercises with pass/fail SLO thresholds. Hand the resulting test matrix to Azure Load Testing for execution.

Does this skill run load tests or execute performance benchmarks?

No, it only plans. It produces a test matrix and load model that Azure Load Testing tooling executes separately, along with observability hooks needed to measure each SLI in production.

What inputs are needed for performance and SLO planning?

You need business goals from the BRD, critical user journeys, stated NFRs from the PRD, traffic assumptions such as expected and peak concurrency, and accuracy expectations like false-positive tolerance. Missing inputs are flagged as assumptions to validate.

When should I not use an SLO planning skill?

Do not use it for executing load tests, security threat modeling, RAI assessment, or privacy and compliance planning, which belong to specialist skills. It also should not author or restate PRD requirements; it cites existing NFR and FR ids instead.