// Shared orchestration patterns for all workflow orchestrators. NOT an executable skill - provides reference documentation for phase execution, state management, interactive mode, and initialization. All orchestrators reference these patterns.
| name | orchestrator-framework |
| description | Shared orchestration patterns for all workflow orchestrators. NOT an executable skill - provides reference documentation for phase execution, state management, interactive mode, and initialization. All orchestrators reference these patterns. |
| user-invocable | false |
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.
Reduce duplication across orchestrators by documenting common patterns once:
→ Pause, → AUTO-CONTINUE) — these are the only two transition types; see orchestrator-patterns.md § 2 for semanticsorchestrator-state.yml schema and operationsEach 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`
| 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) |
All orchestrators follow these principles:
orchestrator-state.yml is source of truth.maister/docs/INDEX.md throughoutdevelopment (bug fixes, enhancements, features)performancemigrationresearchThis skill does NOT get invoked directly. It exists to:
When building new orchestrators, reference these patterns rather than duplicating them.
Unified orchestrator for all development tasks. ALWAYS execute when invoked — never skip for 'straightforward' tasks. Phases adapt based on detected task characteristics rather than predetermined types. Use for any development work that modifies code.
Orchestrates the complete migration workflow from current state analysis through implementation to compatibility verification. Handles technology migrations, platform changes, and architecture pattern transitions with adaptive risk assessment, incremental execution, and rollback planning. Use when migrating technologies, platforms, or architecture patterns.
Orchestrates performance optimization workflows using static code analysis to identify bottlenecks (N+1 queries, missing indexes, O(n^2) algorithms, blocking I/O, memory leaks). Accepts optional user-provided profiling data. Reuses standard specification, planning, implementation, and verification phases.
Interactive product/feature design orchestrator. Transforms fuzzy ideas into structured product briefs through collaborative exploration, iterative refinement, and visual prototyping. Adaptive phases detect design complexity and adjust depth.
Orchestrates comprehensive research workflows from question definition through findings documentation. Handles technical, requirements, literature, and mixed research types with adaptive methodology, multi-source gathering, pattern synthesis, and evidence-based reporting. Supports standalone research tasks and embedded research phase in other workflows.
Unified orchestrator for all development tasks. ALWAYS execute when invoked — never skip for 'straightforward' tasks. Phases adapt based on detected task characteristics rather than predetermined types. Use for any development work that modifies code.