The Operations Stack

Claude skills for operations teams cover the structured, recurring documentation work that keeps organizations running — from weekly status reports and runbook maintenance to capacity planning and vendor risk reviews. This stack is built for BizOps and RevOps teams, operations leads, and project managers who own a wide operational surface area and need consistent output without rebuilding formats from scratch each time.

What these skills do

Operations Status Report

Generate weekly or monthly status reports with KPIs, risks, and action items. Takes project tracker activity and produces a readable narrative with green/yellow/red status indicators, surfaced risks, and decisions that need stakeholder attention. Useful for leadership updates, cross-functional syncs, and board reporting.

Operations Runbook

Write and maintain runbooks for repeatable operational processes — step-by-step procedures, decision trees, escalation paths, and the documentation that makes processes executable by anyone on the team, not just whoever built them. Reduces key-person dependency.

Operations Process Documentation

Document business processes in a clear, structured format — current state, steps, owners, inputs and outputs, and the edge cases that cause problems when they’re not captured. The deliverable that makes onboarding faster and process improvements easier.

Operations Process Optimization

Identify and redesign inefficient processes — bottleneck analysis, waste identification, improvement options, and the structured approach to process change that produces a recommendation rather than just a list of observations. Covers both tactical fixes and systemic redesign.

Operations Capacity Plan

Build capacity plans that connect resource supply to workload demand — headcount projections, utilization analysis, hiring timelines, and the planning structure that helps leadership make resourcing decisions with enough lead time to act on them.

Operations Risk Assessment

Conduct structured operational risk assessments — risk identification, likelihood and impact scoring, mitigation options, and the risk register format that gives leadership a clear picture of operational exposure without requiring them to dig through raw analysis.

Operations Vendor Review

Assess vendor relationships systematically — performance against SLAs, risk exposure, contract terms, renewal decisions, and the vendor review format that supports procurement decisions and escalations.

Operations Compliance Tracking

Track operational compliance requirements — control status, evidence collection, gap identification, and the compliance tracking structure that keeps audits manageable and prevents last-minute scrambles. Useful for ISO, SOC 2, and internal audit preparation.

Operations Change Request

Structure and communicate operational change requests — scope definition, impact assessment, approval requirements, rollback plan, and the change management documentation that gets changes through governance without unnecessary friction.

Who this is for

• BizOps and RevOps teams managing cross-functional operational workflows
• Operations leads responsible for process documentation and operational planning
• Project managers tracking status, risks, and capacity across multiple workstreams
• Chiefs of staff who own operational reporting and cross-functional coordination

For the strategic layer above operations, see the Executive & C-Suite Stack. For infrastructure operations (CI/CD, incident response, platform engineering), see the DevOps & Platform Stack.