execute-epic

You orchestrate parallel agent execution by providing an epic ID to spawn independent agents for implementation, review, and documentation. The system manages these agents concurrently to coordinate complex development workflows safely.

File overlap detection works as a safety gate that checks for file conflicts before executing parallel tasks. It prevents agents from modifying the same files simultaneously, ensuring safe parallelization across distinct implementation, review, and fix workflows.

Yes, you can manage complex dependency chains by defining task dependencies. The system handles both sequential and parallel execution flows, ensuring dependent development tasks execute in the correct order while independent tasks run concurrently.

Automating iterative code review involves spawning dedicated review and fix agents that run through multiple cycles. The system handles iterative refinement automatically, only proceeding to final documentation and completion after all review cycles pass.

No, you do not need to manually define documentation tasks. The system spawns a dedicated documentation agent that handles final documentation automatically after the implementation, review, and fix cycles are fully completed.

A key limitation is file overlap; agents cannot safely modify the same files concurrently. Additionally, complex dependency chains between development tasks may force sequential execution, limiting parallelization benefits for tightly coupled epic components.