pick-next-shell

# Pick Next Shell Pick the next shell from `.turbo/shells/` whose dependencies are satisfied, then carry it through the planning pipeline: expand → refine → self-improve → halt. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Scan shells and pick next 2. Run `/expand-shell` skill 3. Run `/refine-plan` skill 4. Run `/self-improve` skill 5. Mark plan ready 6. Summarize and halt ## Step 1: Scan Shells and Pick Next Check terminal conditions first: - **No shells and no plans** — nothing to pick; stop - **No shells, but plans exist with `status: done` for all** — the project is complete; stop - **No shells, but plans exist with a non-`done` status** — there are unfinished plans; stop If shells exist in `.turbo/shells/`, glob `.turbo/shells/*.md` and read each file's YAML frontmatter. A shell's `depends_on` entry is satisfied when `.turbo/plans/<dep-slug>.md` exists with `status: done` in its frontmatter. - **Candidates** — shells whose `depends_on` are all satisfied - **Blocked** — shells with one or more unsatisfied `depends_on` If there are no candidates (everything is blocked), report which shells are blocked and which dependencies they're waiting on, then stop. If multiple candidates exist, pick the one with the lowest shell number (from the `NN-` prefix `/draft-shells` gives each file). If ambiguous, use `AskUserQuestion` to let the user choose. State the picked shell path and its dependencies before continuing. ## Step 2: Run `...