apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Universal planning entry: analyze task complexity and route to a direct change or a plan file. Use when the user asks to \"plan this task\", \"plan and implement\", or \"run /turbo:plan\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill plan --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill plan -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill plan -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill plan -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill plan -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill plan -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill plan -a windsurf -y
name: plan description: "Universal planning entry: analyze task complexity and route to a direct change or a plan file. Use when the user asks to \"plan this task\", \"plan and implement\", or \"run /turbo:plan\"."
Analyze task complexity to recommend an execution mode, then let the user set the final route.
Categorize the user-supplied task along these dimensions using subjective judgment. This analysis makes the recommendation informed:
Modes are named by what they produce: no plan, or a plan file.
| Mode | Criteria | Route | |---|---|---| | **Direct** | Clear scope, with any remaining decisions small enough to settle in conversation rather than write down. Aligns on the shape, then implements. | Read [references/direct-mode.md](references/direct-mode.md) and follow its steps. | | **Plan** | The approach warrants writing down before implementing — to survey patterns, settle architectural decisions, or survive a fresh session. Produces a plan file, however large the work turns out to be. | Read [references/plan-mode.md](references/plan-mode.md) and follow its steps. |
Form a recommended route from the dimensions and criteria above. Output the recommendation as text: the recommended mode and a line or two on why it fits over its neighbor.
Then use `AskUserQuestion` to have the user set the final route. Offer the recommended mode first, marked "(Recommended)", alongside the other mode; the auto-appended "Other" lets the user describe a different path.
Add a third **Get a second opinion** option whenever committing to the wrong mode would cost a session of rework, and whenever the recommended mode does not earn "(Recommended)" with conviction. It runs the `/consult-codex` skill for the soundest route given the task's scope, stakes, and unknowns. Then resolve the route with that answer in hand, re-asking when the choice stays the user's.
Carry the confirmed route into its reference file from the table above and follow its steps.
A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.