universal-orchestrator-rules

Define governance, delegation, and context hygiene rules for Codex orchestrator behavior.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/amaledtuning/CODEX_Skills --skill universal-orchestrator-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: universal-orchestrator-rules
Source: https://github.com/amaledtuning/CODEX_Skills/tree/main/skills/universal-orchestrator-rules
Command: npx skills add https://github.com/amaledtuning/CODEX_Skills --skill universal-orchestrator-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The universal orchestrator rules provide a reusable governance baseline to govern Codex orchestration, delegation, and incident handling across projects.

Core Features & Use Cases

  • Governance baseline for subagent routing, route integrity, and context hygiene.
  • Enables safe delegation and responsible main-thread boundaries, with companion skills for decomposition, execution, and memory.
  • Use cases include auditing orchestrator behavior, standardizing delegation contracts, and ensuring continuity across sessions.

Quick Start

Review the repository and initialize the universal orchestrator baseline in your project.

Frequently Asked Questions about universal-orchestrator-rules

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

FAQPage Schema
What is orchestrator governance for subagent routing and context hygiene?

Orchestrator governance defines delegation contracts, role boundaries, and read/write separation to standardize subagent routing, maintain context hygiene, and ensure safe main-thread behavior across multiple project wrappers.

How do I standardize delegation contracts for Codex subagents?

You standardize delegation contracts by applying a reusable baseline that specifies role boundaries, route integrity, and incident reporting rules, ensuring consistent and safe subagent delegation across different projects.

Can I reuse the same orchestration rules across multiple project wrappers?

Yes, the universal orchestrator rules are designed as a reusable baseline that applies governance, context hygiene, and route integrity across multiple project wrappers for session continuity.

When do I need a baseline for orchestrator incident reporting?

You need an incident reporting baseline when auditing orchestrator behavior or ensuring continuity across sessions, as it provides standardized rules for documenting route integrity and delegation anomalies.

Does this governance baseline enforce read/write separation for subagents?

Yes, the governance rules specify read/write separation and compact delegation contracts to establish responsible main-thread boundaries and maintain strict context hygiene during subagent operations.