large-change

Plan multi-day refactors by drafting a design doc, decomposing the effort into Phase 1 tasks and Phase 2 milestones, and defining incremental development steps with release checklists to ensure cross-team coordination and structured execution.

Plan breaking changes using a phase-based workflow that emphasizes risk management through documented tradeoffs, alternatives, and rollback strategies. This ensures cross-team coordination with explicit release criteria to avoid production disruptions.

Decompose a large feature by drafting a design doc and breaking it down into Phase 1 tasks and Phase 2 milestones. This task decomposition supports incremental development and cross-cutting coordination across teams.

You need a formal design doc when coordinating significant features, multi-day refactors, breaking changes, or phased subsystems. It defines the structured workflow, documents tradeoffs, and establishes rollback strategies for cross-team coordination.

Yes, the phased workflow supports cross-cutting coordination for complex subsystems by defining explicit milestones, reviews, and release criteria. It structures end-to-end changes with task decomposition and incremental development.