databricks-job-operator

Databricks job orchestration is automated by adopting the databricks-job-operator agent role to guide task execution and produce agent-aligned artifacts such as implementation plans and architecture deliverables. It uses repository context to ensure tasks follow proper sequencing and scope rules.

A Databricks job-operator agent is a role definition that guides task execution within the Databricks workflow remit. It reads agent definitions to deliver structured artifacts like plans, QA findings, and architecture deliverables while maintaining critical rules and sequencing.

QA findings for a Databricks workflow are generated by operating as the databricks-job-operator agent and following the deliverables defined in the agent definition file. This ensures findings align with the agent's mission and repository context.

Yes, agent orchestration supports Databricks architecture deliverables by adopting the databricks-job-operator role to guide execution. It ensures architecture outputs align with the agent remit and maintain proper sequencing within the repository context.

Yes, operating as a databricks-job-operator requires reading the agent definition located in the repository. This file contains the mission, critical rules, and deliverables needed to maintain proper task scope and sequencing.

The job-operator agent for Databricks workflow automation is limited to tasks that clearly match its remit, such as plans and architecture deliverables. It enforces strict sequencing and scope rules, meaning tasks outside the agent definition are not supported.