SkillVaultskills Browse all 500 skills

Data · Version 1.3.0 · Reviewed 2026-08-02

Data Lineage Mapper

Make data systems more correct and operable for column-level lineage and impact analysis with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Traces columns from source to dashboard so impact analysis and incident scoping become possible.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Column-level lineage
  • Impact analysis
  • Incident scoping

How Data Lineage Mapper works

You provide

Schema, volumes, and the queries that actually run

It inspects

Access patterns and skew affecting column-level lineage

It decides

A impact analysis design with migration ordering

You verify

Row counts and checksums compared before cutover

What it checks first

Data Lineage Mapper traces columns from source to dashboard so impact analysis and incident scoping become possible. Use it when the work involves Column-level lineage, Impact analysis, Incident scoping.

  1. The real access patterns, since schema quality is meaningless without the queries it serves.
  2. Cardinality, skew, and growth rate of the key columns.
  3. Consistency and freshness requirements per consumer.
  4. Whether the model preserves history or overwrites it, which determines what questions remain answerable.

Failure modes it recognizes

  • A schema optimized for writes that makes the dominant read pattern a full scan.
  • Skewed partitioning concentrating load on one node.
  • Nullable columns encoding several meanings, making every downstream query ambiguous.
  • A pipeline silently dropping late-arriving records and under-reporting totals.

Answers it will reject

  • Normalizing or denormalizing by preference rather than by measured access pattern.
  • Adding a column for each new requirement until the table encodes multiple entities.
  • Backfilling without a reconciliation check that proves completeness.

Decision rules it applies

  • Design from the read path backward for read-heavy systems.
  • Make invalid states unrepresentable with constraints rather than conventions.
  • Version the schema and treat consumer compatibility as a contract.

Evidence it asks for

  • Profile real query patterns and volumes before proposing a change.
  • Validate migrations with row counts, checksums, and spot comparisons.
  • Monitor freshness and completeness as first-class data-quality signals.

The method inside

  1. Establish what is actually true about column-level lineage from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind impact analysis rather than restating the symptom.
  3. Choose the smallest defensible change for incident scoping, weighing impact, confidence, effort, and reversibility.
  4. Plan migration and observability before cutover

Deliverables

  • Column-level lineage assessment
  • Impact analysis decision and action plan
  • Incident scoping verification checklist

Evidence requirements

  • Schema, access patterns, query plans, or event contracts
  • Volume, cardinality, retention, and freshness
  • Consistency, latency, and migration constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

A source system changed a column and we do not know which of our 300 dashboards are now wrong.

Expected output

Table-level lineage cannot answer this because the blast radius is per column. Build column-level lineage from query logs rather than documentation, then rank affected dashboards by usage so remediation starts where the wrong numbers are actually being read...

Boundaries and compatibility

Ideal for

  • Column-level lineage: produce a decision or artifact grounded in supplied evidence.
  • Impact analysis: produce a decision or artifact grounded in supplied evidence.
  • Incident scoping: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Recommending indexes without a workload
  • Treating eventual consistency as universally acceptable

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.