sdlc-agent-05-mapping-document

Generates source-to-target mapping documents from metadata discovery packages on Databricks.

1|2|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TRRaveendra/AI-Agents-Databricks --skill sdlc-agent-05-mapping-document-trraveendra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-agent-05-mapping-document
Source: https://github.com/TRRaveendra/AI-Agents-Databricks/tree/main/ai-agent-skills/databricks-sdlc-agent-skills/05-mapping-document-agent
Command: npx skills add https://github.com/TRRaveendra/AI-Agents-Databricks --skill sdlc-agent-05-mapping-document-trraveendra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires databricks-sdk, and includes references (resource) components.

What problem does it solve? Data engineering teams need consistent, validated source-to-target mapping documents during the SDLC, but producing them manually from metadata discovery results is slow and error-prone. This Skill acts as Agent 5 in a 15-agent Databricks pipeline, turning a Metadata Discovery Package into a contract-validated mapping_document.json artifact stored in the lakehouse. ## Core Features & Use Cases - Mapping Generation: Produces source-to-target table/column mappings, transformation logic, lookup/join logic, SCD strategy, and incremental vs full-load decisions per target entity. - Contract Validation: Returns JSON matching a strict output schema, with one repair retry on validation failure and routing to human review when clarification is needed. - Lakehouse Integration: Writes artifacts to /Volumes/{catalog}/state/artifacts/{ticket}/ and logs runs to state.artifacts and state.agent_runs for full auditability. - Use Case: After the Metadata Discovery Agent profiles source systems for a Jira ticket, this agent generates the mapping document that downstream Data Model and PySpark Development agents consume, gated by human approval. ## Quick Start Hand this agent the Metadata Discovery Package for ticket PROJ-123 and ask it to produce the source-to-target mapping document artifact.

Frequently Asked Questions about sdlc-agent-05-mapping-document

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

FAQPage Schema
How do I generate a source-to-target mapping document on Databricks?

Provide the Metadata Discovery Package from the upstream agent, then this agent calls the Databricks Foundation Model API to produce table/column mappings, transformation logic, and SCD strategy. The result is validated against a JSON contract and written to the ticket's artifact path in Unity Catalog Volumes.

Can I call Genie Code from a Databricks job or orchestrator?

No, Genie Code is UI-only with no public API for headless invocation. Use the Foundation Model API (Model Serving pay-per-token endpoints like databricks-claude-sonnet-4-5) or a Mosaic AI Agent endpoint for code and document generation instead.

What happens when the mapping document fails contract validation?

The agent gets one repair retry with the validation error appended to its context. If it still fails, the run is routed to state.needs_human so the approval-gate reviewers can inspect it before downstream agents proceed.

Does this agent use the Genie Agents Conversation API?

No, this agent has no natural-language data-querying step, so it does not need the Genie Agents API. That API is reserved for agents 3, 4, 8, and 15, which answer ad-hoc profiling and business-metric questions.

What happens when upstream metadata is missing or contradictory?

The agent returns status needs_clarification with specific questions instead of inventing metadata or business rules. It never fabricates citations; every citation must reference a retrievable UC table, prior artifact path, or Genie conversation ID.