Post Incident Record (PIR)

Discover issues from PagerDuty, Datadog, Cloudflare, and Rollbar concurrently, auto-determine severity, and produce completed PIR forms for each issue.

Inputs

Raw arguments: $ARGUMENTS

Infer from the arguments:

• QUERY: what to investigate. Passed directly to each sub-skill. Defaults to "incidents today".
• CF_DOMAIN_ZONE: (optional) Cloudflare domain and zone ID in domain:zone_id format. Passed to the cloudflare-traffic-investigator skill. If not provided, the cloudflare skill will ask the user.

Resolved during Step 1 (not provided directly):

• SINCE: UTC ISO8601 start of analysis window. Auto-derived from explicit time in QUERY or from PD incident timestamps.
• UNTIL: UTC ISO8601 end of analysis window. Auto-derived from explicit time in QUERY or from PD incident timestamps.
• PD_INCIDENT: PagerDuty incident ID detected from QUERY (triggers PD-first orchestration path).
• SERVICE_HINT: Service name extracted from PD incident (used to scope Datadog/Rollbar queries).
• TITLE_HINT: Incident title extracted from PD incident (used as Rollbar keyword search terms).
• SLACK_CHANNEL: Resolved in Step 2e — from invoker context or $SLACK_INCIDENT_CHANNEL env var. May be a single channel or a comma- or pipe-separated list of channels.