What problem does it solve?
Capture an authoritative, timestamped, and factual record of operational incidents without performing investigation or root-cause analysis, ensuring teams have a neutral source of truth for subsequent workflows.
Core Features & Use Cases
- Enforces factual, non-speculative language and a chronological timeline for incidents.
- Writes a structured Markdown report to docs/incidents/{YYYY-MM-DD_HHMM}_{name}.md using a consistent template including Timeline, Impact, and Current Status.
- Use cases: on-call engineers logging production outages, QA recording reproducible test failures, or monitoring systems summarizing observed errors and raw evidence for handoff to investigators.
Quick Start
Invoke /incident with a concise factual description like "backend returned 429 at 14:02:15 UTC, observed increased error rate and retries" to create the incident report file.