tobihagemann/pick-next-shell
skills/pick-next-shell/SKILL.md
Pick the next shell whose dependencies are satisfied and carry it through planning: expand, refine, self-improve, halt. Use when the user asks to "pick next shell", "next shell", "continue project", "what's next", "next implementation step", or "continue with the plan".
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo pick-next-shellInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 1:24 AM4.8s1 file scanned
SKILL.md
- name:
- pick-next-shell
- description:
- Pick the next shell whose dependencies are satisfied and carry it through planning: expand, refine, self-improve, halt. Use when the user asks to \"pick next shell\", \"next shell\", \"continue project\", \"what's next\", \"next implementation step\", or \"continue with the plan\".
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:
- Scan shells and pick next
- Run
/expand-shellskill - Run
/refine-planskill - Run
/self-improveskill - Mark plan ready
- Halt with next-step instructions
Step 1: Scan Shells and Pick Next
Check terminal conditions first:
- No shells and no plans — tell the user to run
/turboplanfor a new task and stop - No shells, but plans exist with
status: donefor all — report the project is complete and stop - No shells, but plans exist with a non-
donestatus — suggest running/implement-planto finish the remaining plans and 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_onare 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 /expand-shell Skill
Run the /expand-shell skill, passing the shell file path. Capture the resulting plan path for Step 3.
Step 3: Run /refine-plan Skill
Run the /refine-plan skill with the plan path from Step 2. Loops until the plan stabilizes.
Step 4: Run /self-improve Skill
Run the /self-improve skill to compound planning learnings.
Step 5: Mark Plan Ready
Update the plan's YAML frontmatter to status: ready.
Step 6: Halt with Next-Step Instructions
Halt with this message:
Plan ready at
<plan path>.Planning context is likely full, and the plan is comprehensive enough to continue fresh. Run
/clear, then/implement-plan <slug>to implement. After that, run/pick-next-shellagain for the next shell.
Rules
- Do not edit plan files directly. Revisions go through
/refine-plan. - Never modify the spec file.
- Do not attempt to auto-implement. The user drives implementation with
/implement-planin a fresh session. - If a shell file is missing or has invalid frontmatter, halt and report.
Related Skills
tobihagemann/codex-exec
tools
VerifiedTrustedCommunity
Run autonomous task execution using the codex CLI. Use when the user asks to "codex exec", "run codex exec", "execute a task with codex", or "delegate to codex".
334SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/understand-change
tools
VerifiedTrustedCommunity
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
319SKILL.mdUpdated Jun 4, 2026