maestro:agent-base

Multi-agent mission startup is standardized by reading mission context, enforcing baseline health checks, and starting declared services from a single source of truth. This ensures every feature execution follows consistent mission boundaries and validation contracts before feature work begins.

Deterministic service orchestration starts required services from a bootstrap configuration file and waits for health checks to pass. If a service fails its healthcheck, the orchestration stops immediately to prevent unsafe mission execution and maintain system reliability.

Safe handoff reporting is enforced by returning a structured EndFeatureRun report with commands, observations, and discovered issues. If a feature's agentType skill is missing or scope cannot be completed, the agent returns to the orchestrator safely with this structured report.

Yes, this base procedure is required for every mission feature implementation to keep multi-agent runs consistent, reviewable, and safe. It applies to any feature execution where an agent must read mission context, validate baseline health, and orchestrate declared services.

Delegation to a feature-specific skill enforces safety guardrails by separating baseline validation from feature execution. After startup validation completes, the base procedure delegates to the feature's agentType skill, ensuring mission boundaries are maintained and scope is handled correctly.