Data Lineage Documenter

Customizable · 4 variables

Document end-to-end lineage from source systems to dashboards or features, including owners and blast radius.

Prompt

Act as an analytics engineer documenting lineage for incident response. Do not invent hops, owners, or column derivations. Mark unknowns. Downstream asset: [dashboard / mart / feature table] Known upstream systems: [List what you know] Transformation stack: [dbt / Spark / Airflow / other] Evidence you have: [dbt DAG, catalogs, or "thin"] Produce: 1. Upstream to downstream lineage map (text or mermaid) 2. Critical path for freshness 3. Columns that are derived vs raw 4. Ownership at each hop 5. Blast radius if the source breaks 6. Gaps that need discovery interviews 7. The smallest next check to confirm the critical path If the map is mostly guesses, say so in the first line.

LLM

Customize this prompt

4 variables

Progress: 0 of 4 variables filled0%

1Fill Variables

dashboard / mart / feature table*

List what you know*

dbt / Spark / Airflow / other*

dbt DAG, catalogs, or "thin"*

2Generated Prompt

Act as an analytics engineer documenting lineage for incident response. Do not invent hops, owners, or column derivations. Mark unknowns. Downstream asset: [dashboard / mart / feature table] Known upstream systems: [List what you know] Transformation stack: [dbt / Spark / Airflow / other] Evidence you have: [dbt DAG, catalogs, or "thin"] Produce: 1. Upstream to downstream lineage map (text or mermaid) 2. Critical path for freshness 3. Columns that are derived vs raw 4. Ownership at each hop 5. Blast radius if the source breaks 6. Gaps that need discovery interviews 7. The smallest next check to confirm the critical path If the map is mostly guesses, say so in the first line.

Data Lineage Documenter

Customize this prompt

1Fill Variables

2Generated Prompt

Comments

Details