Contract
- Input: source systems, transformation logic, target systems, governance requirements.
- Output: lineage graph + impact analysis + column-level mapping.
- Scope: traces lineage; does not modify pipelines.
- Rule: traces lineage; does not modify pipelines.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit DataLineageArtifact as both:
- JSON:
.agents/skills/platform/artifacts/data-lineage/{identifier}.json
- Markdown view: same filename with
.md extension
Data Lineage
Design data lineage — end-to-end tracing, impact analysis, column-level lineage, and governance support.
Process
1. Inventory sources and targets
- Identify all source systems (databases, APIs, files, streams).
- Identify all target systems (warehouses, lakes, marts, dashboards).
- Capture ownership and SLAs for each system.
Completion criterion: source/target inventory saved.
2. Map transformations
- Extract: ingestion jobs, CDC captures, batch loads.
- Transform: cleaning, enrichment, aggregation, deduplication.
- Load: writes to targets, materialised views, BI exports.
Completion criterion: transformation map saved.
3. Build end-to-end lineage graph
- Nodes: sources, transformations, targets, dashboards, ML models.
- Edges: data flow direction, schedule, volume, freshness.
- Format: directed acyclic graph (DAG) with metadata.
Completion criterion: lineage graph saved (ASCII / Mermaid / diagram).
4. Column-level lineage
- Track column names, types, and transformations per field.
- Capture renaming, type casting, derivation, and aggregation.
- Link business terms to technical columns.
Completion criterion: column-level mapping saved.
5. Impact analysis
- Given a schema change, identify affected downstream assets.
- Prioritise by criticality, usage, and SLA.
- Document remediation steps and communication plan.
Completion criterion: impact analysis report saved.
6. Governance integration
- Tag lineage with data classification (PII, sensitive, public).
- Attach owners, stewards, and retention policies.
- Link to compliance requirements (GDPR, HIPAA, SOX).
Completion criterion: governance tags and policies saved.
Rules
- Rule: trace lineage from source to consumer before declaring impact scope.
- Rule: classify data assets at ingestion time and enforce access boundaries from lineage metadata.
- Rule: separate technical lineage (ETL jobs, queries) from business lineage (reports, dashboards).
- Rule: require owner and steward consent for schema or ownership changes.
- Rule: make lineage queries auditable and retention-aligned with compliance windows.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "data-lineage"3category: "data"4maturity: "stable"5version: "1"6description: "Data lineage (end-to-end tracing, impact analysis, column-level lineage, governance)."7license: "MIT"8capabilities:9 - apply data lineage methods within explicit data boundaries10 - analyze data lineage (end-to-end tracing, impact analysis, column-level lineage, governance) with assumptions, constraints, and failure modes11 - produce and validate a data artifact with evidence, decisions, and next steps12outputs: "lineage graph + impact analysis + column-level mapping."13sideEffects: []14dependencies: []15stopCondition: "Lineage graph saved; impact analysis complete; column mappings documented."16risk: "medium"17trustTier: "3"18maxIterations: "6"19promptVersion: "2.0"20artifactType: "data"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: .agents/skills/platform/fixtures/behavioral/data-lineage.json24diataxis: "how-to"25tags: ["data"]26compatibility: []27approvalRequired: "true"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/data-lineage31---3233## Contract3435- Input: source systems, transformation logic, target systems, governance requirements.36- Output: lineage graph + impact analysis + column-level mapping.37- Scope: traces lineage; does not modify pipelines.38- Rule: traces lineage; does not modify pipelines.39- Rule: documented standards override defaults; explicit project rules take precedence.40- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4142## Provenance4344| Question | Answer |45|---|---|46| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |47| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |48| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |49| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |50| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |51| What risk remains? | Subjective judgment calls, missing context, or external dependency failures525354## Artifact5556Emit `DataLineageArtifact` as both:57- JSON: `.agents/skills/platform/artifacts/data-lineage/{identifier}.json`58- Markdown view: same filename with `.md` extension596061# 62# 63# Data Lineage6465Design **data lineage** — end-to-end tracing, impact analysis, column-level lineage, and governance support.6667## Process6869### 1. Inventory sources and targets70- Identify all source systems (databases, APIs, files, streams).71- Identify all target systems (warehouses, lakes, marts, dashboards).72- Capture ownership and SLAs for each system.7374**Completion criterion:** source/target inventory saved.7576### 2. Map transformations77- Extract: ingestion jobs, CDC captures, batch loads.78- Transform: cleaning, enrichment, aggregation, deduplication.79- Load: writes to targets, materialised views, BI exports.8081**Completion criterion:** transformation map saved.8283### 3. Build end-to-end lineage graph84- Nodes: sources, transformations, targets, dashboards, ML models.85- Edges: data flow direction, schedule, volume, freshness.86- Format: directed acyclic graph (DAG) with metadata.8788**Completion criterion:** lineage graph saved (ASCII / Mermaid / diagram).8990### 4. Column-level lineage91- Track column names, types, and transformations per field.92- Capture renaming, type casting, derivation, and aggregation.93- Link business terms to technical columns.9495**Completion criterion:** column-level mapping saved.9697### 5. Impact analysis98- Given a schema change, identify affected downstream assets.99- Prioritise by criticality, usage, and SLA.100- Document remediation steps and communication plan.101102**Completion criterion:** impact analysis report saved.103104### 6. Governance integration105- Tag lineage with data classification (PII, sensitive, public).106- Attach owners, stewards, and retention policies.107- Link to compliance requirements (GDPR, HIPAA, SOX).108109**Completion criterion:** governance tags and policies saved.110111## Rules112113- Rule: trace lineage from source to consumer before declaring impact scope.114- Rule: classify data assets at ingestion time and enforce access boundaries from lineage metadata.115- Rule: separate technical lineage (ETL jobs, queries) from business lineage (reports, dashboards).116- Rule: require owner and steward consent for schema or ownership changes.117- Rule: make lineage queries auditable and retention-aligned with compliance windows.118119## Completion120121- the skill's completion criteria are explicitly checked122- the artifact is saved and validated123- any blockers or skipped validations are documented124- the next consumer is identified or the work is handed off125---126@include .agents/skills/platform/contract-base.xml