references/orchestration.md

# Multi-agent SQL work policy

A skill file is an instruction document, not an independently running subagent. Delegate only when a host exposes genuine agent tools, with separate contexts and traceable results. If unavailable, execute roles serially.

A lead analyst establishes dialect, objective, data boundaries, desired grain and expected evidence. For substantial tasks, specialists may independently examine (1) correctness and cardinality, (2) dialect/optimizer, (3) write safety/security and (4) test design. Avoid many agents for trivial SQL.

Separate write ownership, prohibit concurrent production mutations, and keep reviewers read-only. Each specialist returns artifact paths, observations, assumptions, actual test commands/results, risks and unresolved questions. The lead reconciles conflicts rather than blindly averaging recommendations.

Never invent agent runs, query results, credentials or successful deployment. External writes and high-impact operations require scoped approval under the host's policies.