Operational Design

SkillMonitoring & ops

Design and improve operational processes, controls, metrics, vendors, and scaling models through bounded pilots and evidence. Do not use for engineering delivery, financial modeling, technology evaluation, or legal advice.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Operational Design skill

What this skill tells your AI

The instructions your AI receives, as published by magnus919/agent-skills in operational-design/SKILL.md and read by ahel’s review.

COO methodology for designing and scaling operations, managing compliance, selecting and managing vendors, and measuring operational health. These frameworks help a COO build the systems and processes that enable the organization to execute reliably at scale.

Domain Model

DomainCoversArtifact
Process DesignValue stream mapping, BPMN, bottleneck analysis, workflow optimizationProcess maps, VSM current/future state
Scaling Frameworks10-to-100-to-1000 transitions, organizational design, delegation patternsScaling plan, org design
Operational MetricsKPI design, balanced scorecard, leading vs lagging indicatorsOperations dashboard
Compliance & AuditSOC 2, ISO 27001, GDPR readiness, audit preparationCompliance roadmap, control matrix
Vendor ManagementRFP process, SLA design, vendor scorecards, relationship tiersVendor management framework
Organizational PatternsTeam topologies, Conway's Law, Dunbar's number, span of controlTeam design, communication model

When to Load

Load this skill when the task involves:

  • Mapping and optimizing a business process (value stream, BPMN)
  • Planning organizational scaling through growth phases
  • Designing operational KPIs and a balanced scorecard
  • Preparing for SOC 2, ISO 27001, or GDPR compliance
  • Running an RFP or vendor selection process
  • Designing SLAs and vendor scorecards
  • Restructuring teams using team topologies
  • Analyzing bottlenecks and throughput constraints
  • Designing delegation and span-of-control models

Loading Order

skill_view('operational-design')                    # This — methodology index
skill_view('strategy-frameworks')                    # Shared decision frameworks
skill_view('artifact-pyramids')                      # Output contract
skill_view('operational-design', file_path='references/process-design.md')
skill_view('operational-design', file_path='references/scaling-frameworks.md')
skill_view('operational-design', file_path='references/operational-metrics.md')
skill_view('operational-design', file_path='references/compliance.md')
skill_view('operational-design', file_path='references/vendor-management.md')

Reference Files

ReferenceLoad WhenFile
Process DesignYou need to map, analyze, or optimize a business processreferences/process-design.md
Scaling FrameworksYou're planning organizational growth or restructuringreferences/scaling-frameworks.md
Operational MetricsYou're designing KPIs, dashboards, or a balanced scorecardreferences/operational-metrics.md
Compliance & AuditYou're preparing for SOC 2, ISO 27001, or GDPR compliancereferences/compliance.md
Vendor ManagementYou're running an RFP, designing SLAs, or evaluating vendorsreferences/vendor-management.md
Decision WorkflowYou need a bounded operating-model choice, pilot, KPI, control, or owner handoffreferences/decision-workflow.md

Design Principles

  1. Process before automation. Automating a bad process makes bad output faster. Map and optimize the workflow before selecting tools.
  2. Scale is a discontinuous function. An organization that works at 10 people will break at 50, 200, and 1,000 — each requires a different operating model. Design for the next phase, not the current one.
  3. Lead with leading indicators. Lagging indicators tell you what already happened. Leading indicators tell you what will happen. A good operations dashboard has a balanced mix of both.
  4. Compliance is a system, not a project. SOC 2 certification is not a one-time effort. Compliance requires embedded controls, continuous monitoring, and periodic testing.
  5. Vendors are partners, not passengers. The cheapest vendor is usually the most expensive in total cost. Invest in vendor relationships proportional to business criticality.
  6. Structure follows strategy. Team topology should be driven by the communication patterns the work requires (Conway's Law), not by reporting lines that are convenient for management.

Related Skills

  • strategy-frameworks — CEO-side strategic direction, competitive analysis, and shared decision frameworks
  • technology-radar — CTO-side technology evaluation and architecture governance
  • financial-modeling — CFO-side unit economics and SaaS metrics
  • artifact-pyramids — output contract specification

Signals

GitHub stars
78
Forks
8
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
operational-design
Source
github.com/magnus919/agent-skills