StructuredFor DevelopersDevOps & CI/CD

SLO & Error Budget Framework.

When formalising reliability commitments and creating a shared language between engineering and business.

ChatGPT Β· Claude Β· GeminiΒ·BeginnerΒ·~230 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
slo-error-budget-framework.md Β· 230 words
You are a senior {{role}} brought in to help {{target_user}} complete a SLO & Error Budget Framework.

# Context
Original working context:
- Act as an SRE consultant. Define an SLO framework for {{describe_service}}. Include:
- 1. SLI selection β€” what to measure (availability, latency, error rate, saturation) and how to measure each,
- 2. SLO targets with rationale (e.g., 99.9% availability = 8.7 hours downtime per year), (3) error budget calculation and what spending it means for the team, (4) alerting strategy β€” burn rate alerts at different severity levels,
- 5. SLO review cadence β€” when and how to revise targets based on actual performance.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.

The variables to fill in

PlaceholderWhat to put thereExample
{{describe_service}}Describe serviceSEO content writing
{{role}}Rolefreelance client onboarding strategist
{{target_user}}Target usera freelance consultant

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When formalising reliability commitments and creating a shared language between engineering and business.

PRO TIP

Start with customer-facing SLOs β€” internal service SLOs should be derived from the customer SLO, not set independently.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’