pick-next-prompt

Solid

Pick the next ready shell from a prompt plan in .turbo/prompt-plans/ and hand it to /turboplan for fill-in. Use when the user asks to "pick next prompt", "next prompt", "continue prompt plan", "what's next", "next implementation step", or "continue with the plan".

AI & Automation 312 stars 24 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
83
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Pick Next Prompt Pick the next ready shell from a prompt plan index at `.turbo/prompt-plans/<slug>.md` and hand it to `/turboplan` in shell mode. ## Step 1: Resolve the Prompt Plan Index Determine which prompt plan index to read 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/prompt-plans/<slug>.md` 3. **In-progress wins** — Glob `.turbo/prompt-plans/*.md`. If exactly one index has any prompt with `Status: in-progress`, use it. This is the prompt plan currently being worked on. 4. **Single file** — If exactly one index file exists, use it 5. **Most recent** — If no index has an in-progress prompt and rule 3 did not resolve, use the most recently modified file 6. **Legacy fallback** — If `.turbo/prompt-plans/` does not exist but `.turbo/prompts.md` exists, tell the user to re-run `/create-prompt-plan` to upgrade to shells, and halt. 7. **Nothing found** — If no prompt plan exists, tell the user to run `/turboplan` for a complex task (which will route to `/create-spec` + `/create-prompt-plan`) and stop If multiple files have in-progress prompts (concurrent work in different feature branches), use `AskUserQuestion` to let the user pick. State the resolved index path before continuing. Read the index file. Each prompt entry uses bold-prefixed inline markers under a `## Prompt N:` heading. Parse: - Prompt number and title (from the `## Prompt N: <title>` heading) - S...

Details

Author
tobihagemann
Repository
tobihagemann/turbo
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

pick-next-shell

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".

312 Updated today
tobihagemann
AI & Automation Solid

create-prompt-plan

Decompose a specification file into context-sized shell plans. Each shell captures the wiring invariants (Produces, Consumes, Covers) and high-level Implementation Steps without committing to file paths. Use when the user asks to "create a prompt plan", "break spec into prompts", "decompose spec into sessions", "plan prompts for spec", "generate prompts from spec", or "make prompts from spec".

312 Updated today
tobihagemann
AI & Automation Solid

review-prompt-plan

Review a prompt plan against its source spec: launches an internal prompt plan review and `/peer-review` in parallel and returns combined findings. Use when the user asks to "review my prompt plan", "review my prompts", "check my prompt plan", "critique my prompts", or wants prompt plan feedback before implementation.

312 Updated today
tobihagemann
Data & Documents Solid

turboplan

Analyze task complexity and route to a planning mode. Produces a plan file at .turbo/plans/<slug>.md. Use when the user asks to "turboplan", "run turboplan", "plan this task", "turbo plan mode", "plan and implement", or "use turboplan instead of plan mode".

312 Updated today
tobihagemann
AI & Automation Solid

implement-plan

Execute an implementation plan file produced by /draft-plan or /turboplan. Runs pre-implementation prep, loads task-specific skills by matching plan content against available skill triggers, executes the plan steps, and runs /finalize. Use when the user asks to "implement plan", "implement the plan", "execute the plan", "run the plan", "implement plans/<slug>.md", "start implementing the plan", or starts a fresh session to implement a previously drafted plan.

312 Updated today
tobihagemann