Menu
Handle production incidents, perform root cause analysis, and write blameless post-mortem reports
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Run chaos security engineering tests — AI agent attempts to hack the Sprint output and reports findings to the team
Validate Java and TypeScript code against banking naming conventions, style rules, quality standards, and secure coding practices
Perform OWASP Top 10 security assessments, vulnerability scanning, and PCI-DSS compliance checks
Design test strategies including security testing, write test plans, and identify test scenarios for banking features with DevSecOps integration
Perform STRIDE threat modeling during Sprint Planning for new features and APIs
Run UX review checklist for banking user flows, validate WCAG accessibility compliance, assess security UX patterns, and review customer interface design
| name | incident-response |
| description | Handle production incidents, perform root cause analysis, and write blameless post-mortem reports |
Invoke during production incidents, post-mortem writing, or incident response planning.
# Incident Post-Mortem: [Title]
**Date:** [YYYY-MM-DD]
**Severity:** SEV[1-4]
**Duration:** [X hours Y minutes]
**Impact:** [Number of affected customers/transactions]
## Summary
[1-2 sentence description]
## Timeline (SGT)
| Time | Event |
|------|-------|
| HH:MM | Alert fired |
| HH:MM | Incident declared |
| HH:MM | Mitigation applied |
| HH:MM | Service restored |
## Root Cause
[Technical explanation]
## Contributing Factors
- [Factor 1]
- [Factor 2]
## Action Items
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| 1 | [Action] | [Name] | [Date] | Open |
## Lessons Learned
- [What went well]
- [What could be improved]