business-operations-skills

# Business Operations — Domain Orchestrator The 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. ## When to invoke | Symptom | Sub-skill to route to | |---|---| | "Where does the work spend most of its time waiting?" | `process-mapper` | | "Is this vendor delivering against the SLA?" | `vendor-management` | | "Do we have enough people to ship in Q3?" | `capacity-planner` | | "I need to brief the company on a re-org" | `internal-comms` | | "Write me a runbook for the incident response process" | `knowledge-ops` | | "Why is our software spend up 40% YoY?" | `procurement-optimizer` | ## Routing logic (deterministic) The orchestrator classifies the inquiry by **signals** detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question. ### Signal table | Signal class | Keywords | Sub-skill | |---|---|---| | **PROCESS** | bottleneck, cycle time, waiting, handoff, BPMN, process map, workflow | `process-mapper` | | **VENDOR** | vendor, supplier, SLA, contract, third-party, MSA, SaaS subscription, renewal | `vendor-management` | | **CAPACITY** | headcount, capacity, utilization, planning, hiring sequence, FTE | `capacity-planner` | | **COMMS** | all-hands, internal new...