SOP Gap Audit

Skill files

The public post is only the explanation. Use these links to inspect or download the actual reviewed skill artifact.

skill.mdDownload SKILL.mdevalDownload evals.json

Skill Overview

Operations teams often inherit SOPs that describe the ideal process but miss the real failure points: exception paths, unclear owners, undocumented handoffs, weak evidence capture, stale systems, or metrics no one can actually collect. The sop-gap-audit Codex skill gives Operations Managers a repeatable way to evaluate whether an SOP is ready to publish, needs owner review, or should be held until operational risks are fixed.

The skill is intentionally narrower than generic SOP writing. It focuses on auditing a draft, stale, inherited, or incident-prone SOP against supplied evidence and producing a decision-ready gap register, owner matrix, update backlog, and rollout note.

Intended Role

This skill is designed for Operations Managers, BizOps leads, process owners, team leads, and functional operators who maintain recurring business processes across teams. It is useful before publishing onboarding runbooks, updating access reviews, closing audit findings, standardizing warehouse workflows, revising finance operations procedures, or turning repeated support escalations into better internal operating documentation.

Required Inputs

• SOP material such as a draft SOP, current SOP, checklist, runbook, wiki page, process map, workflow transcript, training notes, ticket history, audit finding, incident retrospective, or stakeholder notes.
• Process context such as owner, team, trigger event, terminal state, audience, systems used, handoff teams, approval rules, service targets, control requirements, and known pain points.
• Evidence such as cycle-time data, rework rates, audit findings, escalation records, training questions, exception logs, customer or internal complaints, screenshots, or operator feedback.
• Target outcome such as publish, refresh, onboard, close an audit gap, reduce rework, standardize exceptions, or brief stakeholders.

The skill can still run with incomplete inputs, but it labels assumptions and missing evidence instead of inventing process facts.

Expected Output

The skill produces:

• Executive summary with process name, audit purpose, readiness rating, top risks, and recommended decision.
• SOP scope check covering trigger, end state, included paths, excluded paths, audience, systems, and owner.
• Gap register for missing, ambiguous, stale, duplicated, risky, unowned, unmeasurable, or untrainable elements.
• Exception-path review for edge cases, overrides, escalations, failure modes, approvals, reversals, and rollback steps.
• Ownership and handoff matrix by accountable role, supporting team, approval authority, and unresolved owner gaps.
• Control and evidence review for required checks, proof artifacts, audit trail, privacy/security considerations, and retention needs.
• Metrics and operating signals such as cycle time, error rate, rework rate, SLA/SLO, volume, aging, adoption, training completion, and review cadence.
• Prioritized update backlog with owners, effort, risk, dependencies, and acceptance criteria.
• Rollout plan covering communication, training, migration from the old process, effective date, review date, and escalation channel.
• Paste-ready stakeholder note.

Validation Scenario

The included eval set checks three realistic Operations Manager situations:

• An enterprise customer onboarding SOP with missing billing, security, legal, support-contact, kickoff exception, and metric instrumentation steps.
• A contractor access-review SOP with audit evidence weaknesses, timing mismatches, missing vendor roster ownership, and unclear app-owner review responsibilities.
• A warehouse damaged-inventory SOP with photo standards, perishable handling, regulated SKU controls, weekend escalation, finance handoff, and cycle-time reduction goals.

The expected outputs verify that the skill keeps the process boundary clear, rates readiness conservatively, identifies concrete owner/control/exception/metric gaps, prioritizes must-fix risks, and produces job-ready operations handoff language.

Operational Limits

This is a low-risk analysis and documentation workflow. It does not approve policies, replace legal, security, compliance, finance, HR, quality, or safety review, alter systems of record, notify employees or customers, execute controls, or publish the final SOP automatically.

Operations Managers should review the output with the accountable process owner and any legal, compliance, security, finance, quality, HR, customer-facing, or safety owner before using it as an approved operating procedure.

Maintenance Expectations

Review this skill when the organization’s process governance model, document-control requirements, approval authority, audit evidence standards, access-control expectations, training workflow, or operating metric definitions change. Refresh evals when new recurring SOP failure patterns appear, such as vendor handoff gaps, AI-assisted workflow controls, system migration issues, regional compliance variants, or unsupported manual workarounds.

Related Existing Skills

I did not find a close public skill dedicated specifically to SOP gap audits and rollout readiness for Operations Managers. The closest public resources are broader SOP writers, business-operations orchestrators, process mappers, operations playbooks, and general gap-analysis tools. The airoweb artifact differs by treating the SOP as an operations-control object: it checks owner clarity, exceptions, evidence, metrics, training, maintenance cadence, and whether the document is ready to publish.

• SOP Writer: a Claude Code skill for generating structured SOPs, checklists, runbooks, decision trees, and escalation paths. The airoweb skill starts after or alongside drafting and focuses on auditing gaps and rollout risk.
• Business Operations Skills: a broad business-operations orchestrator that routes process documentation, vendor SLA, capacity planning, internal comms, SOP, and procurement requests. The airoweb skill is narrower and does not route across multiple BizOps lanes.
• Process Mapper: a process-improvement skill for measuring process flow, bottlenecks, handoffs, and improvement payback. The airoweb skill can use process evidence but is focused on the SOP document’s readiness, controls, exceptions, and maintainability.
• Gap Analysis & Strategic Planning: a broader skill for operational capability gaps, technology investments, maturity scoring, and strategic roadmaps. The airoweb skill narrows the gap-analysis frame to one SOP and the operating risks that block publication.
• AI Tools for Operations Managers: a directory-style set of Claude Code playbooks for operations managers covering SOPs, compliance audits, vendor evaluation, policy documentation, and change management. The airoweb skill is a reusable Codex skill artifact for one repeatable audit workflow.
• Miro AI SOP Generator: an adjacent AI tool for creating SOPs and process documentation. The airoweb artifact is not a generic generator; it is a structured review pass over an SOP and its operational evidence.
• Hyperproof Gap Assessment Guide: a useful adjacent reference for structured gap assessment against governance, risk, and compliance standards. The airoweb skill adapts the gap-assessment discipline to everyday operations SOP readiness rather than a full compliance framework.