Skill

orchestrator-framework

Provides shared reference documentation for orchestration patterns in maister plugin workflow orchestrators, including phase execution, state management, interactive mode, and initialization.

documentation

developer-tools

npx claudepluginhub skillpanel/maister --plugin maister-copilot

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This skill provides **shared reference documentation** for all orchestrator skills in the maister plugin. It is NOT an executable skill - orchestrators reference these patterns and implement them for their specific domain.

Supporting Assets

references/orchestrator-creation-checklist.mdreferences/orchestrator-patterns.md

SKILL.md

Similar Skills

orchestrator-framework

Provides shared reference documentation for orchestration patterns in maister plugin workflow orchestrators, including phase execution, state management, interactive mode, and initialization.

2 files

maister

orchestrator-discipline-meta-docs

Indexes Orchestrator Discipline docs on orchestration patterns, delegation rules, and context window management. Auto-loads when relevant to Claude plugin coordination.

orchestrator-discipline

orchestration

Orchestrates multi-agent workflows with parallel pipelines, sync barriers, state tracking, checkpointing, and progress metrics. Use for coordinating 3+ agents across sessions.

18 files12 tools

jerry

Stats

Parent Repo Stars66

Parent Repo Forks4

Last CommitMar 16, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Orchestrator Framework

This skill provides shared reference documentation for all orchestrator skills in the maister plugin. It is NOT an executable skill - orchestrators reference these patterns and implement them for their specific domain.

Purpose

Reduce duplication across orchestrators by documenting common patterns once:

Phase Blocks: Simple phase structure with inline transitions (→ Continue, → Pause, → Conditional)
State Management: orchestrator-state.yml schema and operations
Phase Gates: Pause behavior and user prompts
Initialization: Task directory setup, metadata, task creation patterns

How Orchestrators Use This

Each orchestrator reads the framework reference file at initialization (Step 1):

### Step 1: Load Framework Patterns

**Read the framework reference file NOW using the Read tool:**

1. `../orchestrator-framework/references/orchestrator-patterns.md`

Reference Files

File	Purpose
`references/orchestrator-patterns.md`	Delegation rules, interactive mode, state schema, initialization, context passing, issue resolution
`references/orchestrator-creation-checklist.md`	Authoring checklist for creating new orchestrators (not loaded at runtime)

Key Principles

All orchestrators follow these principles:

State-Driven Execution: orchestrator-state.yml is source of truth
Resume Capability: Any orchestrator can be paused and resumed
Interactive: Pause after each phase for user review
User-Confirmed Rollback: Never auto-rollback without user approval
Task Progress: Always track progress with TaskCreate/TaskUpdate tools
Standards Discovery: Reference .maister/docs/INDEX.md throughout

Orchestrators Using This Framework

development (bug fixes, enhancements, features)
performance
migration
research

NOT an Executable Skill

This skill does NOT get invoked directly. It exists to:

Provide discoverable documentation for orchestrator patterns
Serve as single source of truth for common logic
Enable consistent behavior across all orchestrators

When building new orchestrators, reference these patterns rather than duplicating them.