it-automation-governance

Designs and reviews production-safe IT automations, scripts, workflows, and remediation runbooks.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/lwokeray/cowork-plugins --skill it-automation-governance-lwokeray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: it-automation-governance
Source: https://github.com/lwokeray/cowork-plugins/tree/main/plugins/it-operations-cowork/skills/it-automation-governance
Command: npx skills add https://github.com/lwokeray/cowork-plugins --skill it-automation-governance-lwokeray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? IT automations often reach production without identity controls, idempotency, rollback paths, or accountable owners, causing duplicate writes, silent failures, and unrecoverable changes. This Skill provides a structured design contract, workflow, and readiness gate to make automations predictable, bounded, observable, and reversible. ## Core Features & Use Cases - Automation Design Contract: Defines objectives, triggers, inputs, identity and minimum permissions, approval checkpoints, idempotency, batching, retries, audit fields, secrets handling, monitoring, and rollback before implementation. - Agentic Action Policy: Sets explicit boundaries for what an AI agent may gather, draft, and execute, requiring human approval for privilege elevation, deletion, isolation, or broad external changes. - Production Readiness Gate: Requires evidence across ten gates including dry-run review, pilot execution, failure/idempotency testing, rollback testing, and owner approval before labeling an automation production ready. - Use Case: An IT admin wants to schedule a PowerShell script that disables stale accounts across tenants. Use this Skill to produce a design covering identity resolution, dry-run deltas, per-target audit results, and a disable switch before any write occurs. ## Quick Start Ask the assistant to review your automation script or runbook for production readiness using the it-automation-governance design contract and readiness gate.

Frequently Asked Questions about it-automation-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a PowerShell automation safe for production?▼

Define a design contract covering identity, minimum permissions, input validation, dry-run deltas, idempotency keys, batching, retries, and rollback before implementation. Then pass a ten-gate readiness review including pilot execution, failure testing, and owner approval.

What should an IT automation design review checklist include?▼

Include objective and scope, trigger and inputs, identity and permissions, approval boundaries, idempotency and retry behavior, audit fields, secrets handling, monitoring and ownership, rollback or disable switch, and test, pilot, and acceptance evidence.

Can an AI agent safely run IT administration actions?▼

An agent may gather, correlate, draft, and perform low-risk writes when user intent is explicit and the platform provides approval and audit. It must not infer authorization for privilege elevation, deletion, device isolation, or data restore, and must read back state after approved actions.

Why does my scheduled automation create duplicate records?▼

Duplicates occur when writes lack a stable idempotency key and pre-write lookup. Add idempotent operations with correlation IDs, and read back ambiguous results before retrying to avoid repeated writes.

When should IT automation not be used?▼

Avoid automation for one-time read-only investigations, unapproved bypasses of administrative or security processes, and destructive workflows with no recovery path or accountable owner. Preserve a manual safe path for critical services.