databricks-architect

Adopt the Databricks Architect role to produce plans and architecture deliverables.

21|4|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alexeyban/databricks-lab --skill databricks-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: databricks-architect
Source: https://github.com/alexeyban/databricks-lab/tree/main/skills/databricks-architect
Command: npx skills add https://github.com/alexeyban/databricks-lab --skill databricks-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables an agent to operate within the Databricks Architect role by providing role-specific guidelines and repository context.

Core Features & Use Cases

  • Reads and adopts the agent definition to ensure outputs align with Databricks architecture deliverables.
  • Guides task execution to produce plans, designs, implementations, and architecture artifacts for real-world Databricks projects.
  • Keeps scope bounded to the documented remit of the Databricks Architect.

Quick Start

Follow the workflow to adopt the Databricks Architect role by reading the Agents/databricks_architect.md and applying its mission to your task.

Frequently Asked Questions about databricks-architect

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

FAQPage Schema
How do I plan a Databricks architecture for a new data workflow?

Planning a Databricks architecture involves adopting role-specific guidelines to produce structured plans, designs, and implementation artifacts that align with project workflows. The agent executes a defined workflow to generate architecture deliverables based on repository context.

What is the Databricks Architect role in task execution?

The Databricks Architect role provides role-specific guidelines and repository context to ensure task outputs align with architecture deliverables. It keeps scope bounded to the documented remit of planning, designing, and implementing Databricks architectures.

How do I generate architecture documentation for Databricks projects?

Generating architecture documentation requires reading the defined agent workflow and applying its mission to your task. This workflow alignment enables the creation of structured plans, designs, and architecture artifacts for Databricks implementations.

Can I use this approach for non-Databricks data architecture workflows?

No, this approach is scoped exclusively to Databricks architectures. It keeps task scope bounded to the documented remit of the Databricks Architect, ensuring outputs align specifically with Databricks plans, designs, and implementations.

What are the limitations of using an agent for Databricks architecture planning?

The primary limitation is scope boundaries; the agent keeps task execution strictly bounded to the documented remit of the Databricks Architect. It relies entirely on reading specific definition files to produce architecture deliverables, preventing actions outside this workflow.