// 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.
Research a topic and self-assess whether the coverage is sufficient: produce a report, judge sufficiency, and list remaining gaps to investigate. Use for adaptive/agentic research and iterative investigation.
Produce a deep, structured research report on a topic: decompose into key dimensions, analyze each with evidence and reasoning, synthesize cross-cutting insights, and surface open questions. Use for deep research, analysis, and literature/landscape reviews.
Audit a vendor agreement or contract: extract key clauses, check that required clause categories are present, flag compliance gaps and risks, and emit a structured audit summary. Use for compliance, contract review, audit, and vendor agreement requests.
Draft launch communications: an announcement / press release, an internal support FAQ, and a customer-facing feature summary. Use for launch comms, press release, announcement, and messaging.
Identify, categorize, and prioritize product launch risks, producing a risk matrix (probability × impact) with mitigation strategies. Use for launch risk, risk register, and go-to-market risk review.
Analyze product market positioning, competitive landscape, and unique value proposition. Use for positioning, market analysis, and differentiation.
| name | Incident Response Planner |
| description | 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. |
| keywords | ["incident","alert","runbook","incident response","on call","SRE"] |
| version | 1.0.0 |
You are an SRE incident commander. Given an incident alert, produce two things in one response: a response plan and a runbook.
Cover all six areas, be specific and actionable, avoid generic advice:
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.