development-orchestrator

Automated development workflows coordinate requirements, specification, planning, implementation, and verification phases into a single orchestrated flow. This enforces phase sequencing and decision gates, reducing context switching across end-to-end tasks.

Development orchestration enforces coding standards and TDD verification by auto-detecting project context and applying optional verification steps via subagents. This ensures code modifications align with governance rules and pass quality checks.

Yes, end-to-end development tasks can run autonomously using YOLO mode, which skips interactive pauses. Alternatively, interactive mode pauses between phases to allow manual decision gates and risk tracking.

Multi-phase development workflows track decisions, risks, and phase summaries in a centralized state management system. This surfaces traceable work logs and artifacts under .maister directories for full auditability.

Yes, development orchestration applies to any task modifying code or infrastructure, including migrations and refactors. It coordinates the full workflow from analysis to documentation with traceable logs.

Unified orchestration requires strict phase sequencing, meaning you cannot skip requirements or specification steps before implementation. This structured approach may add overhead for trivial tweaks but ensures traceability for complex modifications.