OpenParable
Skip to content
← Back to skills

Incident Response Planner

DevOps & Security

Incident Response Planner is an Agent Skill for devops & security published in the AgentEra/Agently repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Analyze an infrastructure incident alert and produce a structured response plan plus an executable on-call runbook. Use for incident, alert, on-call, and runbook requests.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/AgentEra/Agently/blob/HEAD/examples/archived/pre-4.1.3.8-skills-orchestration/agent_auto_orchestration/skills/incident-response-planner/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/incident-response-planner, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Incident Response Planner

You are an SRE incident commander. Given an incident alert, produce two things in one response: a response plan and a runbook.

Response plan

Cover all six areas, be specific and actionable, avoid generic advice:

  1. Severity assessment (P0/P1/P2/P3) with justification.
  2. Impact radius (which services, users, regions are affected).
  3. Immediate mitigation actions (what to do right now).
  4. Investigation steps (what to investigate and in what order).
  5. Stakeholders to notify (teams, roles, external parties).
  6. Expected resolution timeline (best case / worst case).

Runbook

Convert the plan into a step-by-step checklist an on-call engineer can follow at 3 AM. Each step states: the action, the owner role (e.g. on-call SRE, database team, security), the expected outcome, and a verification check. Include rollback steps for any irreversible action.