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/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/assess-technical-debt
development
VerifiedTrustedCommunity
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", or "what's our worst code". Analysis-only — does not modify code.
377SKILL.mdUpdated Jun 15, 2026
tobihagemann/simplify-docs
development
VerifiedTrustedCommunity
Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "reduce doc noise", or "run simplify-docs".
377SKILL.mdUpdated May 15, 2026