operations-design

Create operations design documents using ITIL 4, SRE, and DevOps practices.

7|4|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/windschord/claude_skils --skill operations-design
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: operations-design
Source: https://github.com/windschord/claude_skils/tree/main/operations-design
Command: npx skills add https://github.com/windschord/claude_skils --skill operations-design

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill provides industry-trend research and a service-ready operational design built on ITIL 4, SRE, and DevOps best practices. It emphasizes factual, non-speculative analysis, a question-driven data collection process using AskUserQuestion, and contextual conversation logs to ensure consistency and traceability.

Core Features & Use Cases

  • Industry trend research and technology scouting
  • System/service scoping and requirement gathering
  • ITIL 4, SRE, DevOps-aligned operational design
  • Comprehensive operational design documentation
  • Consistency checks and objective reviews
  • AskUserQuestion-driven questioning and answer capture
  • Conversation logs for context management

Quick Start

  • Begin with a request: "ι‹η”¨θ¨­θ¨ˆζ›Έγ‚’δ½œζˆγ—γŸγ„" or "ι‹η”¨θ¨­θ¨ˆγ‚’ζ”―ζ΄γ—γ¦γ»γ—γ„"
  • Proceed through industry trend research, service specification, and design sections
  • Validate each section with the user, then perform consistency checks
  • Save the design document, and log results in the conversation log

Frequently Asked Questions about operations-design

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

FAQPage Schema
How do I create an operations design document for a new service?β–Ό

Operations design documents capture service requirements, deployment architecture, and operational procedures. Start by gathering service specifications through structured questioning, research industry best practices for your deployment type (cloud-native, IaaS, or on-prem), then apply ITIL 4 and SRE principles to design operational workflows, SLOs, and runbooks. Document decisions with conversation logs for traceability.

What's included in an ITIL 4 and SRE-based operational design?β–Ό

An operational design covers service scoping, functional and technical requirements, SLO/SLI/SLA definitions, incident response procedures, monitoring strategy, deployment topology, and change management aligned to ITIL 4 and SRE frameworks. The design is template-driven, fact-based, and validated against consistency checks to ensure completeness and alignment with DevOps practices.

Can I use this for cloud-native and on-premises deployments?β–Ό

Yes, operational design applies to cloud-native, IaaS, and on-premises deployments. The design process adapts to your infrastructure type, incorporating industry trends and best practices relevant to your chosen platform, ensuring SLO/SLI/SLA definitions and operational procedures fit your specific deployment context.

How does conversation logging improve operational design consistency?β–Ό

Conversation logs capture all decisions, requirements elicitation, and design rationale throughout the process. This audit trail ensures traceability, enables consistency validation across design sections, and provides context for future operational reviews and changes without losing the reasoning behind each decision.

Do I need DevOps experience to create an operational design?β–Ό

The design process uses structured questioning to elicit requirements from you, regardless of DevOps background. Industry trend research and template-driven drafting guide the design; however, understanding your service's technical requirements, deployment environment, and organizational constraints helps produce more accurate operational specifications.

What's the difference between operational design and service specification?β–Ό

Service specification documents what the service does and its functional requirements; operational design specifies how to operate, monitor, support, and scale it in production. Operational design builds on specifications and adds deployment topology, incident response, SLO/SLA targets, and DevOps/SRE procedures aligned to ITIL 4 frameworks.