orchestrator-framework

You can standardize phase execution and state management across maister orchestrators by adopting shared orchestration patterns from a centralized framework reference. It provides defined frontmatter, standard state schemas, and initialization guidance to ensure consistency across development, performance, migration, and research workflows.

Orchestration patterns for task lifecycles include defined phase execution, standard state schemas, and delegation rules. These patterns ensure consistent progress tracking, initialization, and resume behavior across all orchestrators, reducing duplication and accelerating new workflow creation.

Yes, the orchestration framework is explicitly designed to be applied across development, performance, migration, and research workflows. It provides a single source of truth for phase patterns and delegation rules to ensure consistent execution regardless of the workflow type.

The best way to reduce duplication when creating new maister orchestrators is to consult centralized reference documentation for shared orchestration patterns. This provides a single source of truth for phase execution, state handling, and initialization, accelerating onboarding and new orchestrator creation.

Yes, the framework includes reference guidance for both interactive and YOLO modes of task execution. It defines how orchestrators should handle initialization and phase progression in either mode to maintain consistent task lifecycles and resume behavior.