Define SLOs for this feature based on the examples. Examples: Requirement: "Checkout must be fast and reliable" SLOs: - Latency: p99 < 500ms for checkout completion - Availability: 99.95% success rate for payment processing - Error budget: 21.6 minutes downtime/month Requirement: "Search should return relevant results quickly" SLOs: - Latency: p95 < 200ms for search queries - Relevance: Top 3 results contain user intent 90% of time - Availability: 99.9% for search endpoint Feature requirement: {{requirement}} User impact level: {{impact_level}} Current baseline: {{baseline_metrics}} Define appropriate SLOs with justification.
SLO Definition from Requirements
Derive SLOs from product requirements using calibrated examples.
93 copies0 forks
Share this prompt:
Details
Category
CodingUse Cases
SLO definition workshopReliability planning supportProduct requirements translation
Works Best With
claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared