recipe-implement

End-to-end implementation workflows are automated by orchestrating multiple sub-agents that handle requirement analysis, layer routing, design reviews, testing, and readiness gating. You initiate the deployment workflow by supplying a project brief and desired environment to trigger automated planning and execution.

Yes, autonomous task execution across monorepo-style projects is supported through coordinated orchestration, layer routing, and per-task execution cycles. The system applies strict constraints and step gating to manage requirements and ensure completeness across the software development lifecycle.

Sub-agent orchestration works by spawning agents according to operator rules and enforcing safety checks at each step. The workflow applies step gating and readiness constraints to ensure completeness before moving forward, satisfying subagents-orchestration-guide requirements for autonomous execution mode.

To start an automated deployment workflow, you need to provide a project brief containing your requirements and the desired target environment. The orchestration system uses these inputs to perform requirement analysis, plan the workflow, and trigger autonomous execution.

Yes, the implementation workflow enforces design reviews and readiness gating before deployment. It applies enforced safety constraints and gatekeeping across steps to ensure all testing and completeness requirements are strictly satisfied during the software development lifecycle.

An orchestrated sub-agent workflow should be used for complex software development lifecycles requiring coordinated requirement analysis, layer routing, and autonomous execution. It is particularly suited for monorepo-style projects where enforced safety constraints and step gating are needed to ensure deployment readiness.