tracing-downstream-lineage

Trace downstream data lineage and assess impact across tables, DAGs, and dashboards.

419|61|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/astronomer/agents --skill tracing-downstream-lineage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracing-downstream-lineage
Source: https://github.com/astronomer/agents/tree/main/skills/tracing-downstream-lineage
Command: npx skills add https://github.com/astronomer/agents --skill tracing-downstream-lineage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace downstream data lineage and impact analysis to answer questions like what depends on this data, what breaks if it changes, and which assets rely on it. This helps data teams assess risk and prioritize changes before touching production tables, DAGs, or dashboards.

Core Features & Use Cases

  • Identify direct consumers across tables, DAGs, and dashboards using a complete downstream view.
  • Build a dependency tree that maps downstream assets and their relationships.
  • Categorize change risk by criticality to surface owners and trigger appropriate approvals.
  • Guidance for typical workflows like changing a table schema, updating a DAG, or modifying a data pipeline, with stakeholder recommendations.

Quick Start

Begin by examining the target's direct consumers, then expand to downstream dependencies to complete the blast radius picture. Review DAGs, dashboards, and BI jobs that read from the target. Use this to decide safe change windows and stakeholder communications.

Frequently Asked Questions about tracing-downstream-lineage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace downstream data lineage to assess impact before changing a table schema?

Tracing downstream data lineage involves mapping direct consumers like tables, DAGs, and dashboards to build a dependency tree. This identifies the blast radius and surfaces asset owners to help assess risk before modifying production sources.

What is the best way to find out what breaks if a data pipeline or schedule changes?

Finding what breaks requires an impact analysis that builds a complete downstream dependency tree. By reviewing connected BI jobs and dashboards, you can categorize change risk by criticality and identify affected stakeholders before applying modifications.

How does downstream impact analysis help identify stakeholders for data dependencies?

Downstream impact analysis identifies stakeholders by surfacing the owners of dependent assets within the dependency tree. Categorizing change risk by criticality triggers appropriate approvals and ensures the correct downstream consumers are notified.

Can I use this to map the blast radius of a DAG modification across dashboards and pipelines?

Yes, you can map the blast radius of a DAG modification by expanding from direct consumers to all downstream dependencies. This process reviews connected dashboards and pipelines to provide a complete view of what relies on the target asset.

When do I need to perform downstream lineage tracing on my data tables?

You need downstream lineage tracing when modifying production tables, updating DAGs, or changing data pipelines. It helps decide safe change windows and guides stakeholder communications by assessing the risk of breaking dependent dashboards and BI jobs.