pattern-orchestration-complex

Complex multi-file tasks are coordinated using a four-phase orchestration workflow across planning, execution, verification, and cleanup. This process enforces upfront planning, requires explicit user approval before execution, and maintains atomic commits for safe rollbacks.

You need complex workflow orchestration when a task affects four or more files or takes over an hour to complete. This disciplined process reduces risk and accelerates delivery by enforcing phase-by-phase progress tracking and explicit user approval.

Start planning a large multi-file execution by creating an execution plan with pattern-task-breakdown. Present the generated plan to the user for explicit approval, then proceed through disciplined task-by-task execution and final verification.

Quality assurance during multi-file execution is ensured by integrating pattern-retry into the verification phase. Executing one task at a time with atomic commits enables clean rollbacks and supports disciplined quality control throughout the workflow.

No, the orchestration workflow processes one task at a time during the execution phase. This ensures atomic commits and clean rollbacks, which are critical for maintaining stability across complex multi-file changes.

The four-phase orchestration workflow requires upfront planning and explicit user approval before proceeding, which may slow down rapid prototyping. It is designed for complex tasks affecting four or more files rather than simple, quick modifications.