orchestrator

You can enforce the master build sequence for incident management services by loading an orchestrator skill first to coordinate phase dependencies, service scaffolding, and wiring validation. It strictly enforces phase order and defines completion criteria for each step.

Phase dependency management in incident system architecture is the process of controlling the required build order and inter-service connections. It centralizes control over scaffolding to prevent misconfigurations and dependency failures across all incident management services.

You need to load an orchestrator for incident system scaffolding at project initiation and whenever resuming or transitioning between phases. It determines what to build next, which services to scaffold, and how to validate completion.

To define the criteria for phase completion when building incident systems, the orchestrator establishes definitions of done for each phase. These criteria provide clear guidance for completion at each step and coordinate handoffs between inter-dependent services.

Yes, the build sequence orchestrator works for resuming paused incident management projects by applying session governance. It loads relevant architecture and service skills at session start to determine the current phase and coordinate what to build next.