project

Multi-file refactors require structured lifecycle orchestration that coordinates discussion, research, planning, wave-based execution, verification, and shipping. This prevents disorganized development by enforcing design approval gates and parallel researcher dispatch before proceeding through ordered execution waves.

Wave-based execution runs task executors in ordered parallel batches with dependency awareness. This mechanism allows complex changes to be broken into sequential waves where independent tasks execute simultaneously while respecting inter-task dependencies before moving to the next phase.

Session state management for interrupted development planning persists human-readable artifacts under a .planning/ directory. This approach enables resumption from existing progress, allowing structured quality gates and bounded fix loops to continue seamlessly across sessions without losing context.

Full project lifecycle orchestration applies to ambiguous requirements, dependency-heavy changes, and work requiring structured quality gates before merge. For simpler tasks, an escape hatch routes you to quick execution instead, helping you avoid unnecessary overhead for trivial changes.

Code changes require passing test, lint, and build verification with bounded fix loops before shipping. Diff-based code review validates the implementation against the validated plan, ensuring structured quality gates are met before the pull request automation phase executes.

Lifecycle orchestration supports git worktrees for parallel development by coordinating researcher agents and task executors across isolated branches. The planning phase validates dependencies before execution waves, ensuring worktree-based changes merge cleanly through the shipping phase.