executive-operations

Diagnose operational constraints and turn process, vendor, and capacity risks into measurable operating decisions.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill executive-operations-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executive-operations
Source: https://github.com/marcmarti9/agentit/tree/main/skills/executive-operations
Command: npx skills add https://github.com/marcmarti9/agentit --skill executive-operations-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often buy software, add headcount, or automate workflows before understanding what actually constrains reliable throughput. This Skill provides a structured diagnostic method for identifying the binding operational bottleneck and choosing the smallest change that removes it with acceptable risk. ## Core Features & Use Cases - Constraint-first diagnosis: Map demand, owners, handoffs, queues, failure paths, and vendor dependencies to classify the root problem as process, capacity, tooling, policy, vendor, or measurement. - Automation and vendor risk modeling: Evaluate automation payback, exception paths, and rollback plans, plus vendor SLA, switching cost, data portability, and single-source concentration risk. - Decision framework with metrics: Pair lagging outcomes with leading indicators, assign owners and action thresholds, and define rollback and review points. - Use Case: A support team misses SLAs. Use this Skill to map the ticket flow, find that approval delays—not staffing—are the bottleneck, and implement a decision-rights change with a queue-age leading metric. ## Quick Start Use the executive-operations skill to diagnose why our order fulfillment cycle time keeps increasing and recommend the smallest operational change that fixes the constraint.

Frequently Asked Questions about executive-operations

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

FAQPage Schema
How do I find the bottleneck in a business process?▼

Map the current operating flow including demand, owners, handoffs, queues, failure paths, and vendor dependencies. Then classify the primary problem as process, capacity, tooling, policy, vendor, or measurement, and prioritize removing the binding constraint before optimizing other steps.

When should I automate a manual workflow?▼

Automate when the process has clear purpose and ownership, high frequency and manual time, and a stable path with a designed exception path. Model implementation cost, maintenance, integration risk, payback, and rollback before committing.

Should I hire more people or fix the process first?▼

Examine the process first. Before adding headcount to repeatable work, check whether the work can be removed, standardized, simplified, batched, automated, or moved to a clearer owner. Headcount should not substitute for understanding a broken process.

How do I assess vendor lock-in and dependency risk?▼

Inspect SLA versus actual performance, switching and migration paths, data ownership and portability, renewal terms, single-source concentration, and failure fallback recovery time. Critical single-source vendors need a known switching or degradation plan.

What are common mistakes in operational improvement projects?▼

Common failure modes include buying software before diagnosing the process, optimizing non-bottlenecks, automating without exception paths, creating KPIs with no owner or action threshold, and ignoring change management and real human workload.