data-department-orchestratorlisted

Route ambiguous, organizational or multi-role Data Department requests and compose governed workflows with owners, dependencies, gates and handoffs. Use when the named deliverable cannot be built until another role sources, models or certifies its inputs — a dashboard from systems not yet ingested, an incident spanning monitoring, diagnosis and revalidation, a rebuild combining discovery, implementation and proof. The deliverable named last does not decide the owner; the work standing in front of it does. Route personal learning or portfolio projects to Personal Data Project Engineering.
kina2711/data-department-agent-skills · ★ 2 · AI & Automation · score 65

Install: claude install-skill kina2711/data-department-agent-skills

# Data Department Orchestrator ## Operating contract 1. Identify the requested deliverable, then select exactly one atomic task below. 2. Read that task file completely before acting. 3. Read [references/lifecycle-standard.md](references/lifecycle-standard.md) and use the task's profile, risk tier and execution path. 4. Load only the company context and adapter references needed for the selected task. 5. On a cross-role handoff, compare logical ID and SHA-256 in `references/shared-reference-manifest.json`; reuse an already loaded shared reference when both match instead of loading its duplicate. 6. Inspect real artifacts and systems before making change-sensitive claims. 7. Apply Definition of Ready, stage gates, test strategy, Definition of Done, approval and handoff requirements. 8. Do not invent access, approvals, successful execution, test results or business confirmation. 9. For any Git-backed mutation, regardless of the task's verb or profile, require a pre-change success/scope contract, a post-change `core-audit-change-scope`, and fresh `core-verify-deliverable` evidence before completion. 10. For learning, coaching or skill-transition work, resolve [the learner-memory interoperability contract](references/learning-memory-interoperability.md). Reuse only relevant verified summaries; never infer mastery from exposure, and expand stale, uncertain, changed-version or safety-critical prerequisites. ## Role routing Read [references/role-routing.md](references/role-routi