# Operations Workflow

> Route operational work to focused, evidence-based workflows for SOPs, capacity, change, risk, compliance evidence, runbooks, vendor review, stakeholder updates, and process improvement. Use when the user asks for this workflow or needs operational routing without colliding with installed operations capabilities. Turkish triggers: operasyon süreci, SOP veya runbook, işleyişi düzenle ve doğru uzmanlığa yönlendir.

- Skill: `yigityildiz0/operations-workflow` (Agent Skill)
- Install (CLI): `npx skillmds@latest add yigityildiz0/operations-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yigityildiz0/operations-workflow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: yigityildiz0 (https://skillmd.com/u/yigityildiz0)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/yigityildiz0/operations-workflow

---


# Operations

Choose the narrowest workflow that matches the operational decision:

- `capacity-planning` for demand, throughput, staffing, or service scenarios;
- `change-management` for rollout, approvals, rollback, and verification;
- `compliance-evidence-tracking` for controls and evidence, not legal certification;
- `process-documentation` or `process-optimization` for repeatable work;
- `operational-risk-assessment` for cause-event-impact analysis;
- `operations-runbook` for controlled procedures and escalation;
- `vendor-review` for tool or supplier choices;
- `stakeholder-update` for evidence-backed status and asks.

Keep ownership, cadence, input, output, risk, and decision gates explicit. Prefer the smallest useful process over administrative overhead. No operational skill authorizes its own external, destructive, privileged, or production action.