sdlc-agent-13-documentation

Generates README, architecture, deployment, and runbook documents from upstream Databricks pipeline artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Manually assembling project documentation (READMEs, architecture docs, runbooks, KT docs) at the end of a data engineering pipeline is slow and error-prone. This Skill acts as Agent 13 of 15 in the Databricks Multi-Agent SDLC Platform, automatically synthesizing all documentation from the artifacts produced by the twelve upstream agents. ## Core Features & Use Cases - Artifact-grounded documentation: Reads prior agent artifacts from /Volumes/{catalog}/state/artifacts/{ticket}/ and summarizes them without re-deriving facts, ensuring docs match what was actually built. - Contract-validated output: Returns JSON conforming to a strict output contract (status, artifact_path, citations, tokens) that the LangGraph orchestrator validates before handoff to the Deployment Agent. - Databricks backend integration: Calls the Foundation Model API (e.g., databricks-claude-sonnet-4-5) via Model Serving for generation, with guidance on why Genie Code cannot be invoked headlessly. - Use Case: After agents 1-12 complete requirement analysis, data modeling, PySpark/SQL development, and testing for a Jira ticket, this agent produces the README, technical spec, deployment guide, runbook, user guide, and KT document, writes them to the lakehouse, and logs the run to state.agent_runs. ## Quick Start Ask the agent to generate the full documentation set for ticket DATA-1234 from the upstream artifacts in the Databricks volume.

Frequently Asked Questions about sdlc-agent-13-documentation

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

FAQPage Schema
How do I generate project documentation from Databricks pipeline artifacts?

Invoke this agent with the ticket ID; it reads all prior artifacts from /Volumes/{catalog}/state/artifacts/{ticket}/, calls the Foundation Model API to synthesize README, architecture, deployment, runbook, and KT documents, then writes them back to the lakehouse volume.

Can Genie Code be called via API from a Databricks agent?

No, Genie Code is UI-only with no public REST or SDK endpoint 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 output format does the documentation agent return?

It returns JSON matching the output contract with fields for agent name, ticket_id, status (complete, needs_clarification, or failed), artifact_path, summary, citations, tool_calls, tokens, and duration_ms. The LangGraph orchestrator validates this schema before handoff.

What happens when upstream artifacts are missing or contradictory?

The agent returns status needs_clarification with specific questions rather than inventing metadata or business rules. On failed contract validation it gets one repair retry, then routes to state.needs_human for review.

Does the documentation agent support Word document deliverables?

Yes, it can optionally use the docx skill when a Word deliverable is requested. By default it produces Markdown-based documentation artifacts written to the Unity Catalog volume.