OperationsPROPRO REQUIREDFC-OPS-004
Incident Claw
incident-claw
v0.2.0May 22, 2026Incident response — severity classification, blameless post-mortems, and corrective actions that prevent recurrence
How you handle 3 AM pages defines your reliability culture more than any uptime SLA ever will. I structure your incident response around clear severity classifications, blameless postmortems published within 48 hours, and action items that actually get tracked to resolution—not just assigned and forgotten. Incident command isn't a ceremony; it's a practiced skill.
OpenClaw
Hermes
Claude Code
Codex
Cursor
Windsurf
Aider
OllamaPRIMARY ACTION
Unlock with ProCOMPATIBLE WITH
OpenClawHermesClaude CodeCodex+4
8 compatible tools5 output formats
When to Use
- Harden deployment and release workflows
- Improve observability and alert readiness
- Define environment standards
- Prepare operational runbooks
Compatible Frameworks
OpenClawHermesClaude CodeCodexCursorWindsurfAiderOllama8 TOOLS
Quality Gates
- Blameless post-mortem culture
- Incident roles clearly defined
- Corrective actions with assigned owners
- Clear communications per audience
- Complete and structured response
5 GATES DEFINED
Expected Outputs
Incident Postmortem Document (Blameless Format)Severity Classification Guide with ExamplesOn-Call Runbook with Escalation PathsIncident Timeline ReconstructionPostmortem Action Item Tracker
Native exports per tool
OpenClaw10 files
openclaw/AGENTS.mdopenclaw/SOUL.mdopenclaw/TOOLS.md+7 moreHermes5 files
hermes/skills/flickclaw/incident-claw/SKILL.mdhermes/skills/flickclaw/incident-claw/references/workflow.mdhermes/skills/flickclaw/incident-claw/references/quality-gates.md+2 moreClaude Code6 files
claude-code/CLAUDE.mdclaude-code/.claude/skills/incident-claw/SKILL.mdclaude-code/.claude/skills/incident-claw/references/workflow.md+3 moreCodex5 files
codex/AGENTS.mdcodex/.flickclaw/agents/incident-claw/codex.mdcodex/.flickclaw/agents/incident-claw/workflow.md+2 moreCursor3 files
cursor/.cursor/rules/flickclaw-incident-claw.mdccursor/.cursor/rules/flickclaw-incident-claw-workflow.mdccursor/.cursor/rules/flickclaw-incident-claw-quality-gates.mdcWindsurf3 files
windsurf/.windsurf/rules/flickclaw-incident-claw.mdwindsurf/.windsurf/rules/flickclaw-incident-claw-workflow.mdwindsurf/.windsurf/rules/flickclaw-incident-claw-quality-gates.mdAider3 files
aider/CONVENTIONS.mdaider/aider.mdaider/.aider.conf.ymlOllama4 files
ollama/Modelfileollama/system-prompt.mdollama/template.md+1 moreInstall Commands
Install the FlickClaw CLI, then select your AI agent framework below to get the correct install command.
Step 1: Install CLI (one-time)
npm install -g @flickclaw/cli@latestStep 2: Select Framework
OpenClaw
npm exec --yes @flickclaw/cli@latest -- install incident-claw --target openclawDownload as ZIP
Example Prompt
Try this prompt with Incident Claw to see what it can do:
Review the deployment pipeline and monitoring. Identify bottlenecks and single points of failure. Produce Incident Postmortem Document (Blameless Format), Severity Classification Guide with Examples, On-Call Runbook with Escalation Paths.Example Output
IllustrativeWhat a typical Incident Claw report looks like:
# Incident Claw — Assessment Report **Project**: microservices-cluster **Context**: a Kubernetes cluster running 12 microservices with Istio and Prometheus **Generated**: 2026-07-10 ## Executive Summary The Incident Claw completed its review of microservices-cluster (a Kubernetes cluster running 12 microservices with Istio and Prometheus). 3 findings were identified with concrete remediation steps. All quality gates were verified before delivery. ## Findings | # | Severity | Area | Finding | Recommended Action | |---|----------|------|---------|-------------------| | 1 | **P0** | Deployment | No rollback strategy defined for 4 services | Add Helm rollback hooks and deployment pause windows | | 2 | **P1** | Monitoring | Alert fatigue from 200+ low-priority alerts/day | Consolidate alerts, add severity routing, mute during maintenance | | 3 | **P2** | Cost | 3 dev clusters running 24/7 without downscaling | Add cron-based scaling to zero during off-hours | ## Quality Gates - [✓] Severity classification applied within 5 minutes of declaration - [✓] Blameless postmortem published within 48 hours of resolution - [✓] Action items from postmortems tracked to completion ## Outputs Generated - **Incident Postmortem Document (Blameless Format)**: Included in the report above. - **Severity Classification Guide with Examples**: Included in the report above. - **On-Call Runbook with Escalation Paths**: Included in the report above. - **Incident Timeline Reconstruction**: Included in the report above. - **Postmortem Action Item Tracker**: Included in the report above. ## Validation - [x] All quality gates passed (3/3) - [x] 3 findings documented with severity and remediation - [x] 5 output sections generated - [x] Evidence collected and referenced --- *This is an illustrative example output from FlickClaw. Results vary based on project context.*
RELATED AGENTS