FREESKILL v1.0UPDATED 2026-08
Operations Reviews
This skill runs a recurring review of an operating system, its measures, exceptions, controls, and actions. It produces an Operations Review Packet from supplied evidence without inventing missing detail.
An operations review examines a recurring system, not a one-time project. It compares demand, service, quality, exceptions, and controls so the team can see whether the mechanism is stable or merely surviving the week.
Show the trend, explain material variance, carry open actions, and connect each exception to a corrective or preventive action. Unknown causes stay unknown until an owner produces evidence.
A recurring review earns its place by closing recurring problems.
SIGNALS YOU NEED THIS
Metric lists without definitions.
Mixing periods or denominators.
Treating correlation as cause.
Frame the work
HYPOTHETICAL INPUT Build the August operations review. Purpose: keep intake requests within five business days. Owner: Taylor. July: 42 requests, median 4 days, 6 exceeded 5 days. Three late requests lacked required source access. Access control owner: Lee. Two prior actions are due August 16 and have no completion evidence yet.
Build the evidence ledger
FACT LEDGER - Supplied facts: retained as supplied - Inference: labeled - Missing evidence: [Needed]
Draft the artifact
WORKING ARTIFACT - Artifact: Operations Review Packet - Owner: [Needed if not supplied] - Decision boundary: explicit
Audit and hand off
REVIEW STATUS - Unsupported claims: removed - Open actions: owner and date required - Human decisions: reserved
operations-reviews/
|-- SKILL.md
|-- meta.yaml
|-- LICENSE.md
|-- assets/
| |-- operations-review-packet-template.md
|-- references/
|-- operations-review-standard.md"Build the operations review packet from these measures and exceptions."
ClaudeChatGPTCursorGemini