All teams / Operations

Operations

Vendors, processes, change management, capacity planning, compliance tracking.

Ops touches everything: vendors, processes, compliance, capacity, change management. The work is mostly about institutionalizing repeat patterns: turning tribal knowledge into docs, ad-hoc evaluations into scoring matrices, and one-off rollouts into reusable plans. /operations:* is the systematization engine.

Plugins to install

Pick from this set for the role. Primary plugins are essential; companions multiply value.

  • operations primary

    Vendor evaluation, process docs, change management, capacity planning, compliance tracking.

    claude plugin install operations@pace
  • finance companion

    Vendor and procurement workflows touch AP.

    claude plugin install finance@pace
  • legal companion

    Contract review feeds vendor selection.

    claude plugin install legal@pace
  • human-resources companion

    Capacity planning ties to headcount and HR planning.

    claude plugin install human-resources@pace
  • productivity companion

    Cross-team coordination + meeting prep.

    claude plugin install productivity@pace

Connectors to set up

Claude prompts to authorize each one the first time a relevant skill fires. You only do this once per project.

  • (none required; many ops skills work from pasted context)

Workflows

Common ways teams use these plugins day to day. Each one is a starting point; adapt the prompt to your context.

  • Vendor evaluation

    Generates a scoring matrix against your current stack. Considers integration, pricing, security, support.

    /operations:vendor-evaluation $vendor against current stack
  • Document a process

    Turns a tribal workflow into a structured doc: trigger, steps, owner, escalation, edge cases.

    /operations:document-process for $recurring_workflow
  • Change management plan

    Generates a rollout plan for a cross-team migration: comms, stages, rollback, success metrics.

    /operations:change-plan for the new SSO provider migration
  • Capacity planning

    Reads current team data + projected work and surfaces headcount + utilization gaps for the next quarter.

    /operations:capacity quarterly headcount plan
  • Compliance tracker

    Generates and maintains a control tracker for SOC 2, ISO 27001, or similar. Flags overdue items.

    /operations:compliance-tracker SOC 2 controls Q3

Tips & tricks

Field-tested patterns from teams that have already shipped a quarter or two on these plugins.

  • Document the tribal knowledge

    /operations:document-process is the fastest way to capture 'we should write this down' work that lives in people's heads.

  • Vendor matrices > vibes

    /operations:vendor-evaluation generates a real scoring matrix. Beats the slide-of-bullet-points comparison every time.

  • Pair with /legal:* for vendors

    During vendor selection, /operations:vendor-evaluation → /legal:contract-review covers selection and contracting in one flow.

  • Change plans before migrations

    /operations:change-plan is cheap; rollback plans you wrote ahead of time are priceless.

  • Tie capacity to /data

    For honest capacity planning, ground in actual utilization. Pair /operations:capacity with /data:* queries on time tracking or work logs.

  • Compliance is incremental

    /operations:compliance-tracker monthly cadence keeps audit prep from being a fire drill.

See also