Planning Slices

Use this workflow when a change is too large, risky, or cross-cutting to handle as one undifferentiated implementation. The output should be a working plan that future agents can resume from, not a polished proposal.

Core Idea

Plan large changes as ordered slices. Each slice should have a concrete goal, a dependency boundary, expected output, verification, and running findings. A good slice can become a focused PR, commit, or reviewable checkpoint, and should leave the repo in a better state even if later slices are delayed.

When To Use

Use planning slices for:

• migrations and compatibility transitions
• multi-module or multi-service features
• runtime, API, deployment, or UI changes with hidden risk
• staging validation or rollout work
• refactors where one large PR would hide behavior changes
• any task where the next agent needs a reliable handoff record