Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From business-operations-skills
Top-level Business Operations router. Routes the inquiry to one of six BizOps sub-skills (process, vendor, capacity, comms, knowledge, procurement) and returns a digest. Invokes the business-operations-skills orchestrator (context: fork).
npx claudepluginhub msm47/gitskil --plugin business-operations-skillsHow this command is triggered — by the user, by Claude, or both
Slash command
/business-operations-skills:cs-bizops <inquiry>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /cs:bizops — Business Operations router Use the `cs-bizops-orchestrator` agent + `business-operations-skills` orchestrator skill to handle this inquiry: **$ARGUMENTS** ## Routing protocol 1. Classify the inquiry against the six BizOps lanes: - **PROCESS** — bottleneck, cycle time, handoff, workflow → `process-mapper` - **VENDOR** — SLA, third-party risk, SaaS audit → `vendor-management` - **CAPACITY** — headcount, utilization, hiring sequence → `capacity-planner` - **COMMS** — all-hands, change announcement, internal newsletter → `internal-comms` - **KNOWLEDGE** — SOP, ...
Share bugs, ideas, or general feedback.
Use the cs-bizops-orchestrator agent + business-operations-skills orchestrator skill to handle this inquiry:
$ARGUMENTS
Classify the inquiry against the six BizOps lanes:
process-mappervendor-managementcapacity-plannerinternal-commsknowledge-opsprocurement-optimizerIf top lane signal score ≥ 2 keyword hits → invoke that sub-skill in forked context.
If single-signal or tie → ask one clarifying question naming the top two candidate lanes.
After sub-skill runs, return ≤ 200-word digest to the parent context.