plan-phases

Phase sizing divides work into independently executable phases constrained to 30-50k token budgets per phase. Define each phase's goals, acceptance criteria, and dependencies, then sequence them to minimize cross-phase blocking and ensure sub-agent execution feasibility.

Dependency analysis clarifies handoffs and reduces coupling by mapping requirements upfront, identifying which phases block others, and structuring vertical slices by layer, entity, operation, or concern to enable parallel execution where possible.

Structured planning guides you through stepwise requirement gathering, acceptance criteria definition, and phase sequencing with measurable outcomes. Apply vertical-slice splitting and document handoffs so each phase stands alone within budget limits.

Phase-based planning applies to both greenfield and integration scenarios. Dependency minimization and context budget constraints guide the same planning methodology regardless of whether you're building new or integrating with existing systems.

Split the feature vertically by layer, entity, operation, or concern rather than horizontally by stage. Redefine phase boundaries so each phase delivers measurable value independently, reducing scope per phase and clarifying acceptance criteria for handoff.