Operations

Skills (9)

Each skill auto-triggers when its description matches what you're doing, or you can invoke explicitly via the slash command.

• /operations:capacity-plan

  Plan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.

• /operations:change-request

  Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.

• /operations:compliance-tracking

  Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.

• /operations:process-doc

  Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

• /operations:process-optimization

  Analyze and improve business processes. Trigger with "this process is slow", "how can we improve", "streamline this workflow", "too many steps", "bottleneck", or when the user describes an inefficient process they want to fix.

• /operations:risk-assessment

  Identify, assess, and mitigate operational risks. Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, process, or decision.

• /operations:runbook

  Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.

• /operations:status-report

  Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.

• /operations:vendor-review

  Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.

Connectors

MCP servers this plugin integrates with, grouped by category. Bundled servers are pre-configured in .mcp.json. Alternatives slot in via the ~~category placeholder pattern.

How MCP and connectors work → · Full CONNECTORS.md on GitHub →

Source

• Path: plugins/operations
• Author: Anthropic
• Version: v1.2.0
• License: Apache 2.0
• Upstream: anthropics/knowledge-work-plugins/operations

Pace imports this plugin verbatim from upstream. We don't edit it here; customize by forking to a new directory (e.g. plugins/operations-gb/) and registering it separately in the marketplace.