meta-orchestrator

Name: meta-orchestrator
Availability: InStock
Author: dylan-conlin

Coordinate orchestrator sessions and cross-project prioritization with handoff reviews.

Updated Aug 23, 2026

Search Tags:#workflow #session-management #orchestrator #handoffs #pattern-detection #meta-orchestrator

Ready to run

npx skills add https://github.com/dylan-conlin/orch-go --skill meta-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meta-orchestrator
Source: https://github.com/dylan-conlin/orch-go/tree/main/skills/src/meta/meta-orchestrator
Command: npx skills add https://github.com/dylan-conlin/orch-go --skill meta-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires orchestrator.

What problem does it solve?

Meta-orchestrator provides a high-level management layer for orchestrator sessions, enabling cross-project focus, handoff review, and systemic evolution to prevent frame-drift and fragmentation.

Core Features & Use Cases

Frame-shift governance: oversee orchestrator sessions across projects and time.
Handoff review automation: evaluate SESSION_HANDOFF.md, detect friction patterns, and drive improvements.
Strategic decision capture: distinguish WHICH vs HOW decisions and seed KB with decisions and improvements.
System evolution and tooling: propose changes based on recurring friction.

Quick Start

Define a strategic focus, spawn an orchestrator with a refined goal, and monitor the handoff to drive pattern improvements.

Frequently Asked Questions about meta-orchestrator

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

FAQPage Schema

How do I prevent frame-drift across multiple orchestrator sessions?▼

To prevent frame-drift across multiple orchestrator sessions, you need frame-shift governance to coordinate cross-project prioritization, scope meta-level decisions, and enforce spawn discipline. This maintains alignment and prevents fragmentation over time.

What is the best way to manage orchestrator session handoffs?▼

The best way to manage orchestrator session handoffs is to automate handoff review by evaluating SESSION_HANDOFF.md files. This detects friction patterns and drives systemic improvements to reduce future handoff friction.

How do you capture strategic decisions in session management workflows?▼

Capturing strategic decisions in session management workflows requires distinguishing WHICH vs HOW decisions. You then seed the knowledge base with these decisions and improvements to maintain systemic evolution and cross-project focus.

Do I need an orchestrator dependency to use meta-orchestrator for pattern detection?▼

Yes, you need the orchestrator dependency to use meta-orchestrator. It provides a high-level management layer that enforces spawn discipline, guardrails, and pattern detection to oversee and improve existing orchestrator sessions.

When should I not use a meta-level orchestrator for workflow sessions?▼

You should not use a meta-level orchestrator for workflow sessions if you lack recurring friction patterns or cross-project handoffs. It is designed for advanced system evolution and frame-shift governance, not simple, isolated task execution.

Why does orchestrator session fragmentation occur and how can I fix it?▼

Orchestrator session fragmentation occurs due to unmanaged frame-drift across projects and time. You fix it by applying frame-shift governance, enforcing spawn discipline, and proposing tooling changes based on detected friction patterns.