Universal Company Operator System#

A project-agnostic executive team for any company, stage, or industry.

How to Use This System#

Start here: Activate universal_business_operator for any broad or cross-functional request. It classifies the request and routes to the right operator(s).

Go direct: If the request clearly belongs to one function, activate that operator directly.

Operator Directory#

OperatorRoleWhen to Useuniversal_business_operatorMaster Router / OrchestratorAny broad or multi-role requestuniversal_ceo_operatorStrategy, Vision, Executive DecisionsDirection, positioning, priorities, tradeoffsuniversal_product_engineering_operatorProduct, Tech, RoadmapBuild plans, feature specs, tech strategyuniversal_growth_marketing_operatorGrowth, Marketing, FunnelsAcquisition, content, launch, messaginguniversal_sales_partnerships_operatorSales, Revenue, PartnershipsOutreach, deals, distribution, pricinguniversal_operations_coo_operatorOps, SOPs, AccountabilitySystems, workflows, team executionuniversal_finance_operatorBudget, Cash Flow, PricingFinancial planning, runway, profitabilityuniversal_customer_success_operatorOnboarding, Support, RetentionCustomer experience, feedback loopsuniversal_data_analytics_operatorMetrics, Insights, ExperimentsDashboards, analytics, optimizationuniversal_design_ux_operatorUX, Interface, Brand ExperienceFlows, clarity, design systemsuniversal_legal_compliance_operatorLegal, Compliance, ContractsRisk review, policies, regulatory flagsuniversal_community_operatorCommunity, Engagement, AdvocacyDiscord, events, audience development

Routing Logic#

See orchestration.md for full routing table and orchestration flow.

Core Principle#

Every operator understands the project first, then executes its role. No industry-specific assumptions are baked in — this system works for startups, DAOs, agencies, creator brands, nonprofits, and enterprises alike.

File Structure#

text

universal_company_operator_system/
├── SKILL.md                          ← You are here (root entry point)
├── README.md                         ← Human-readable overview
├── orchestration.md                  ← Multi-agent routing and coordination logic
├── operator_manifest.json            ← Machine-readable operator registry
├── universal_business_operator/
│   └── SKILL.md
├── universal_ceo_operator/
│   └── SKILL.md
├── universal_product_engineering_operator/
│   └── SKILL.md
├── universal_growth_marketing_operator/
│   └── SKILL.md
├── universal_sales_partnerships_operator/
│   └── SKILL.md
├── universal_operations_coo_operator/
│   └── SKILL.md
├── universal_finance_operator/
│   └── SKILL.md
├── universal_customer_success_operator/
│   └── SKILL.md
├── universal_data_analytics_operator/
│   └── SKILL.md
├── universal_design_ux_operator/
│   └── SKILL.md
├── universal_legal_compliance_operator/
│   └── SKILL.md
└── universal_community_operator/
    └── SKILL.md

Command Console Mode#

For command-based operation, use COMMAND_CONSOLE.md as the routing layer and OPERATING_SYSTEM.md as the execution layer.

Default syntax:

text

/run [command] [objective]

Example:

text

/run growth create a 30-day launch plan

Command Console Mode remains scoped to this skill pack only. It must not modify broader environments, install dependencies, manage secrets, or assume unavailable tools without explicit user approval.