incident

DE//AGENT currently lists 16 resources under incident: 9 tutorials, 5 runbooks, 1 skill. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Also present: 1 agent.

Documented learning objectives across these resources:

• Write a blameless timeline — via Incident Postmortem Writer
• Separate trigger from contributing factors — via Incident Postmortem Writer
• Convert findings into dated, owned action items — via Incident Postmortem Writer
• Read a failing expectation precisely — column, rule, value — via Respond to a failing quality expectation
• Quantify a failure — how many rows and which ones — via Respond to a failing quality expectation
• Decide block vs quarantine vs pass-with-warning on evidence — via Respond to a failing quality expectation
• Run the reliability checklist over your own pipeline end to end — via Capstone — the reliability checklist for a pipeline you can page on
• Drill the incident path — match the alert, walk the runbook, capture the timeline — via Capstone — the reliability checklist for a pipeline you can page on

22 more objectives live on the individual resource pages.

These resources map to stages: Data Quality (2), Reliability (5), Warehousing (1), Cloud (1), Python + SQL (1), Observability (1), Data Processing (2), Agentic Data Engineering (1), Streaming (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

4 more in the full list below.

How scores are computed: source quality score.

Highest composite score first:

1. Incident Postmortem Writer score 38.9 — beginner
2. Spark job is slow score 36.75 — advanced
3. Spark job suddenly costs 4x score 36.75 — advanced

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Incident Postmortem Writer, Respond to a failing quality expectation, Pipeline failed.

Reach for these with production experience: Spark job is slow, Spark job suddenly costs 4x, The 3am batch incident path.

Security-flagged entries: Incident Postmortem Writer (1 flag), Spark job is slow (1 flag), Spark job suddenly costs 4x (1 flag), Incident drill: a broken upstream caught by freshness and lineage (2 flags), Kafka consumer lagging (3 flags), Incident Assistant (3 flags), CDC stopped (3 flags), Pipeline failed (4 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Incident Postmortem Writer — Structures incident notes into a blameless postmortem: timeline, impact, detection gap, contributing factors, and action items with owners and dates. details
• Spark job is slow — A batch Spark job's runtime has jumped — find whether it is skew, partition count, spill or over-scan. details
• Spark job suddenly costs 4x — One job's compute cost quadrupled without an obvious functional change — attribute it and reverse the regression. details
• Respond to a failing quality expectation — A quality expectation failed in production and bad data may be reaching consumers. Follow the data-quality-failure runbook: read the failure precisely, quantify it, then make the o… details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add incident-postmortem-writer

Incident Postmortem Writer — review first

Adjacent topics: tutorial (9 shared), runbook (3 shared), postmortem (3 shared), cost (2 shared), performance (2 shared), lineage (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.