impact-analysis

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

Documented learning objectives across these resources:

• Read the lineages of an asset from a lineage store — via Lineage Explainer
• Compute a downstream impact set — via Lineage Explainer
• Distinguish technical from business lineage — via Lineage Explainer
• Explain why column-level lineage beats table-level for change impact — via Column-level lineage: the concepts and the event standard
• Read an OpenLineage event and name its Airflow, Spark and dbt integrations — via Column-level lineage: the concepts and the event standard
• Compute a downstream impact set from a lineage store — via Column-level lineage: the concepts and the event standard
• Install and invoke the lineage-explainer skill — via Walkthrough: the lineage-explainer skill, from question to impact set
• Distinguish technical lineage from business lineage in its output — via Walkthrough: the lineage-explainer skill, from question to impact set

4 more objectives live on the individual resource pages.

These resources map to stage: Observability (5). 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.

How scores are computed: source quality score.

Highest composite score first:

1. Lineage Explainer score 35.5 — intermediate
2. Column-level lineage: the concepts and the event standard score 34.15 — intermediate
3. Walkthrough: the lineage-explainer skill, from question to impact set score 34.15 — intermediate

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

Security-flagged entries: Lineage Explainer (2 flags), Lineage tooling in practice: DataHub MCP and the lineage-graph plugin (2 flags), Lineage Graph (3 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Lineage Explainer — Traces column-level lineage from an asset to its upstream sources and downstream consumers, and reports the impact set for a proposed change. details
• Column-level lineage: the concepts and the event standard — Table-level lineage says a job touched a table; column-level lineage says which columns feed which. Learn the concepts, the OpenLineage event model that makes lineage work across t… details
• Walkthrough: the lineage-explainer skill, from question to impact set — Install the lineage-explainer skill and walk it end to end: ask what breaks if a column changes, read technical and business lineage from the store, and produce an impact report wi… details
• Lineage tooling in practice: DataHub MCP and the lineage-graph plugin — Put lineage to work with two tools — a DataHub MCP server that lets an agent search entities and read lineage and schema, and a lineage-graph plugin that turns column-level impact … details

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

npx de-agent-platform add lineage-explainer

Lineage Explainer — review first

amp plugin add de-agent/lineage-graph

Lineage Graph — review first

Adjacent topics: lineage (5 shared), tutorial (3 shared), provenance (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.