Task Splitting Protocol
This playbook is for **Opt-in Slicing Mode** only.
Purpose
This playbook is for Opt-in Slicing Mode only.
Do not load or apply it during normal development. Do not use it for ordinary UI incubation, mock app surfaces, app cards, Storybook stories, copywriting, docs index cleanup, lightweight roadmap sync, app registry display updates, or non-destructive refactors.
Large task size alone is not enough to trigger this protocol.
Activation
Use this protocol only when the user explicitly asks for slicing, RFC-first, ADR-first, phase planning, planning-only work, proceed-gated work, or staged confirmation.
When activated, announce the mode at the beginning of the response so the user can interrupt early if it was unintended.
Splitting Principles
Phase 1 means the first visible implementation slice unless the user explicitly asked for planning-only.
Prefer this order when it fits:
1. First visible implementation slice
2. Contract / type boundary
3. State or data model
4. UI integration
5. API / backend integration
6. Verification
7. Docs syncPlanning-only Phase 1 is allowed only when the user asked for it.
Slice Definition
Keep slice plans under 250 lines. Each slice should document:
Name
Goal
Allowed Files
Forbidden Files
Max Diff Size
Validation Command
User-visible Behavior
Rollback Plan
Next SliceRecommended Slice Sizes
| Size | Files | Approval |
|---|---|---|
| Small patch | 1-3 | Normal |
| Normal patch | 4-8 | Normal |
| Large patch | 9-15 | Explicit user approval |
| More than 15 | Split again |
Patch Mode defaults still favor max 8 changed files and max 2 packages per slice, but implementation should not stop for ordinary Direct Implementation Mode work just because a diff is large.
Scope Expansion Stop Rule
If implementation reveals wider or riskier scope than the user requested, stop and report:
Scope expansion detected.
Original scope:
New required scope:
Why this is necessary:
Recommended safe next step:Do not automatically enter slicing. Ask whether the user wants Opt-in Slicing Mode.
Prox OS Hints
- New official apps can often land directly with manifest, registry, icon, and UI when the work is mock/static UI.
- Window manager, Spaces, app contract, auth, permissions, billing, database, deployment, and destructive migration work are good candidates for opt-in slicing.
- Docs sync should follow implementation unless the user asked for docs-only or planning-only work.