draft-shells

# Draft Shells Decompose a specification file into shells at `.turbo/shells/<spec-slug>-NN-<title>.md`. Each shell represents one unit of work for a separate Claude Code session. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Resolve the source spec 2. Decompose into shells 3. Resolve open questions 4. Write shell files 5. Present summary If the confirmed shell count is one, the Single-Shell Bail-out at the end of Step 2 marks tasks 3-5 deleted via `TaskUpdate` and exits. ## Step 1: Resolve the Source Spec Determine which spec to decompose using these rules in order: 1. **Explicit path** — If the user passed a file path, use it 2. **Explicit slug** — If a slug was passed, resolve to `.turbo/specs/<slug>.md` 3. **Single file** — Glob `.turbo/specs/*.md`. If exactly one file exists, use it 4. **Most recent** — If multiple files exist, use the most recently modified 5. **Legacy fallback** — If `.turbo/specs/` does not exist but `.turbo/spec.md` exists, use it 6. **Nothing found** — If no spec exists, nothing to decompose; stop The slug of the resolved spec becomes the prefix for shell file names: a spec at `.turbo/specs/<slug>.md` produces shells at `.turbo/shells/<slug>-NN-<title>.md`. For the legacy fallback, use slug `legacy`. State the resolved spec path and target shell directory before continuing. Read the spec and identify: - **Scope** — total surface area of work - **Work categories** — UI, backend, data layer, infrastructur...