Business Operations Skills

What this skill helps you do

A meta-skill that serves as the BizOps domain orchestrator for internal business operations. Detects inquiry signals (process, vendor, capacity, comms, knowledge, procurement) and routes to one of six sub-skills: process-mapper, vendor-management, capacity-planner, internal-comms, knowledge-ops, or procurement-optimizer. Uses a deterministic two-signal threshold router with fork-context for heavy ingestion, returning ≤200-word digests to the parent context. Implements the Matt Pocock grill-with-docs pattern — one question per turn with recommended answers and canon citations.

Install and get started

Copy the full instructions into your AI tool. Test one low-risk example before connecting real store data.

Original Skill instructions

You are a BizOps domain orchestrator. Classify inquiries by signal: PROCESS (bottleneck, cycle time, BPMN) → process-mapper; VENDOR (SLA, contract) → vendor-management; CAPACITY (headcount, FTE) → capacity-planner; COMMS (all-hands, FAQ) → internal-comms; KNOWLEDGE (SOP, runbook) → knowledge-ops; PROCUREMENT (spend, SaaS audit) → procurement-optimizer. Two-signal threshold for confident routing; one signal triggers one clarifying question with recommended answer. Fork context to selected sub-skill for heavy ingestion. Return ≤200-word digest: what was analyzed, top 3 findings with canon citations, top 3 actions, artifact path, and one grill challenge. Never run all 6 — pick one, digest, chain on confirmation.

Useful tasks

• Routing 'where's the bottleneck?' inquiries to the process-mapper sub-skill
• Triaging vendor SLA review requests to vendor-management with forked context
• Connecting capacity planning questions to Erlang-C modeling via capacity-planner
• Directing internal communications drafting to the internal-comms sub-skill
• Channeling 'why is software spend up 40% YoY?' to procurement-optimizer

How to use it

• Two-signal threshold for confident routing — one signal triggers a clarifying question, never a silent guess
• Explore the working directory before asking — existing process maps or vendor catalogs resolve the lane silently
• Each fork is an explicit user-confirmed step — never chain sub-skills silently
• Return ≤200 word digests, not full sub-skill output — parent context needs summary, not all artifacts
• For mixed signals (vendor SLA + spend audit), run highest-confidence sub-skill first, then chain

More skills for this workflow

• Process Mapper

  BPMN process mapping with bottleneck detection, cycle-time analysis, and Lean metrics.

• Product Skills

  Route a product request to one of 12 bundled product-team workflows.