Business Operations — Domain Orchestrator
Business Operations — Domain Orchestrator is a routing skill that classifies internal operations inquiries (process, vendor, capacity, comms, knowledge, procurement) and forks to one of six specialized sub-skills, returning a concise digest. It ensures deterministic, repeatable analysis and produces artifacts like process maps, vendor scorecards, or SOPs.
✨ What it does
- Routes inquiries to one of six sub-skills based on keyword signals.
- Asks a single forcing question with a recommended answer when routing is ambiguous.
- Walks decision trees depth-first for cross-lane inquiries, requiring explicit user confirmation before chaining.
- Returns a ≤200-word digest with top findings, next actions, and a grill challenge.
- Produces at least one artifact (markdown, CSV, or JSON) per sub-skill.
- Uses stdlib-only Python tools and does not call external APIs.
🎯 When to use it
- When you need to diagnose a bottleneck or map a business process.
- When you need to evaluate vendor SLA performance or manage supplier contracts.
- When you need to plan capacity or headcount for an upcoming quarter.
- When you need to author internal communications like all-hands decks or change announcements.
- When you need to analyze procurement spend or rationalize SaaS subscriptions.
🚀 How to use
Trigger by describing an internal operations problem, e.g., "BizOps review", "where's the bottleneck", "vendor health", "internal SOP", "all-hands deck", "spend categorization", "capacity for Q3", or "process mapping". The skill will detect signals and route to the appropriate sub-skill, possibly asking one clarifying question. Provide access to relevant data (process docs, vendor lists, spend exports) or accept templated dummy data. Example prompts:
Where does the work spend most of its time waiting?
Is this vendor delivering against the SLA?
Write me a runbook for the incident response process.
📄 Output: Each sub-skill produces at least one artifact (markdown, CSV, or JSON) saved to the working directory, with the file path surfaced in the digest.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/business-operations/skills/business-operations-skills .claude/skills/business-operations-skillsSkill source: business-operations/skills/business-operations-skills/SKILL.md
⚠️ Good to know
Requires an organization of at least 10 employees and access to relevant data; does not store state across sessions and does not call external APIs.
❓ FAQ
What happens if the inquiry has mixed signals, like vendor SLA and spend audit?
The orchestrator runs the highest-confidence sub-skill first, then asks if you want to run the second one in a follow-up forked turn.
Can I run all six sub-skills at once to be thorough?
No, that's an anti-pattern. The skill picks one based on signal, returns a digest, and lets you chain additional sub-skills only after explicit confirmation.
Does the skill edit production process docs directly?
No, it writes to a new file and proposes a diff; it never edits production docs without asking.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.