business-operations-skills

1# Business Operations — Domain Orchestrator
2 
3The BizOps surface is **internal**: how the company actually runs. This orchestrator forks its conversation context, routes your inquiry to one of six sub-skills, then returns a tight digest to the parent thread. The heavy ingestion (vendor catalogs, process interviews, multi-doc SOP intake) stays in the forked context.
4 
5## When to invoke
6 
7| Symptom | Sub-skill to route to |
8|---|---|
9| "Where does the work spend most of its time waiting?" | `process-mapper` |
10| "Is this vendor delivering against the SLA?" | `vendor-management` |
11| "Do we have enough people to ship in Q3?" | `capacity-planner` |
12| "I need to brief the company on a re-org" | `internal-comms` |
13| "Write me a runbook for the incident response process" | `knowledge-ops` |
14| "Why is our software spend up 40% YoY?" | `procurement-optimizer` |
15 
16## Routing logic (deterministic)
17 
18The orchestrator classifies the inquiry by **signals** detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question.
19 
20### Signal table
21 
22| Signal class | Keywords | Sub-skill |
23|---|---|---|
24| **PROCESS** | bottleneck, cycle time, waiting, handoff, BPMN, process map, workflow | `process-mapper` |
25| **VENDOR** | vendor, supplier, SLA, contract, third-party, MSA, SaaS subscription, renewal | `vendor-management` |
26| **CAPACITY** | headcount, capacity, utilization, planning, hiring sequence, FTE | `capacity-planner` |
27…