simple-plan-orchestrator-executor

You can automate multi-stage refactoring by using a sub-agent orchestrator to dispatch specific plan stages into isolated git worktrees. This coordinates execution and merges results only after strict verification, preventing cross-contamination between steps.

The best way to coordinate sub-agent lifecycles is to use an automated orchestration skill that manages staged execution. It dispatches sub-agents for specific tasks, validates their output against acceptance criteria, and handles the final integration.

Yes, you need a structured plan document to automate workflow orchestration for technical migrations. The orchestrator uses this document to coordinate sub-agent tasks, manage git worktrees, and verify implementation stages.

Yes, automated plan execution works with git worktree support for software refactoring. It requires git worktrees to isolate sub-agent tasks during staged execution, ensuring changes are validated against acceptance criteria before merging.

Automated review and integration validates sub-agent output against defined acceptance criteria during multi-step migrations. It ensures each stage is tested and verified before merging the isolated git worktree changes into the main project.

You should not use an orchestrator executor if your project lacks git worktree support or a structured plan document. It is designed for complex, multi-stage technical migrations requiring strict verification, rather than simple, single-step updates.