Split Task

Must read: ../pack-shared/standards.md — Read /taste and /architecture doctrines this turn before splitting lanes or folders. Do not skip.

Ask style: ../pack-shared/asking.md

This skill is a worker step for /task or /just-do-it, not a typical user start.

Split one task or goal into small, ordered inline slice contracts. Keep the result in chat under the shared execution context; do not write an INDEX, plan path, status file, or workspace state.

Slices must name entry/folder per architecture; do not split in a way that forks a service or primitive.

If the user explicitly asks to save the split, get or honor an approved destination and write only that requested artifact.

Smart zone

A slice fits the smart zone when: