operating

Manage live production signals with human-in-the-loop incident response.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/SeaBrad72/sparkwright --skill operating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: operating
Source: https://github.com/SeaBrad72/sparkwright/tree/main/skills/operating
Command: npx skills add https://github.com/SeaBrad72/sparkwright --skill operating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, blast-radius-aware framework for handling live production signals, preventing catastrophic automated actions while ensuring incidents are properly triaged and documented.

Core Features & Use Cases

  • Blast Radius Assessment: Mandates a safety evaluation before any remediation is proposed to ensure changes are reversible and contained.
  • Autonomy Tier Mapping: Categorizes incidents into L0-L3 tiers to define the appropriate level of agentic authority versus human intervention.
  • Loop Closure: Integrates incident response with the discovery phase by scaffolding postmortems and feeding findings back into the project backlog.

Quick Start

Invoke the operating skill to analyze the current production alert by correlating the request id with the trace id and assessing the potential blast radius.

Frequently Asked Questions about operating

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

FAQPage Schema
How do I assess blast radius before proposing incident remediation in production?

Incident response autonomy tiers categorize the appropriate level of agentic authority versus human intervention. Mapping incidents to L0-L3 tiers ensures that remediation proposals require human-in-the-loop validation for critical production system operations.

How do I correlate telemetry trace ids with request ids to triage production alerts?

Postmortem documentation scaffolds the discovery phase by capturing incident response findings and feeding them back into the project backlog. This loop closure ensures production anomalies are properly documented and prevents future recurrences.

Does this incident response framework require integration with an E5 telemetry stack?

This framework distinguishes itself by mandating blast-radius assessment and autonomy tier mapping before any remediation. Unlike automated approaches, it uses a structured, human-in-the-loop operational model to safely manage live production signals.

What are the limitations of automated remediation during live system incidents?

You should not use automated remediation without first assessing blast radius and mapping the incident to an autonomy tier. This framework mandates human-in-the-loop validation for production anomalies to ensure changes remain reversible and contained.