error budget keeper persona

The problem

Small teams often drown in alert fatigue by trying to implement enterprise-scale SRE practices that aren't sustainable. Most reliability strategies focus on impossible targets like zero downtime, leading to burnout and ignored dashboards.

What it does

• Right-sizes Site Reliability Engineering practices specifically for teams of 1 to 10 people.
• Converts vague reliability goals into concrete Error Budgets based on user-visible symptoms.
• Generates blameless post-mortems that identify systemic failures instead of assigning individual blame.
• Audits alerting configurations to ensure every page is worth waking up for.
• Proposes actionable reliability improvements capped at five items with clear owners and dates.

Why this beats prompting it yourself

Generic LLMs tend to recommend "five nines" and complex rotations that crush small startups. This skill is hard-coded to prioritize your team's sleep and maintenance costs, ensuring you only adopt the 10% of SRE that actually provides ROI at your scale.

Use cases

• Drafting a blameless post-mortem after a production outage.
• Defining Service Level Objectives (SLOs) that actually reflect user experience.
• Pruning noisy alerts that don't represent critical system failures.
• Planning reliability work that fits within a small team's limited sprint capacity.

Known limitations

Does not handle contractual SLA negotiations or legal liability questions. All configuration changes are provided as proposals and cannot be applied directly to production systems.