Skill336 repo starsupdated 6d ago

turboplan

Turboplan analyzes task complexity across scope, stakes, and unknowns to recommend whether to implement directly, create a plan file, or develop a spec with shells before coding. Use it when facing ambiguity about the best execution path for a project, particularly when deciding whether exploration and documentation will improve outcomes versus jumping straight to implementation.

View source Repository: turbo

Install in Claude Code

Copy

git clone --depth 1 https://github.com/tobihagemann/turbo /tmp/turboplan && cp -r /tmp/turboplan/claude/skills/turboplan ~/.claude/skills/turboplan

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Turboplan

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:

- **Scope**: single feature / single subsystem vs multi-feature / multi-subsystem
- **Stakes**: one-off change vs long-lived project with architectural implications
- **Unknowns**: clear approach vs needs exploration and product decisions

Modes are named by what they produce: no plan, a plan file, or a spec plus shells.

| Mode | Criteria | Route |
|---|---|---|
| **Direct** | Clear scope and a known approach, ready to implement. Goes straight to `/implement`. | Read [references/direct-mode.md](references/direct-mode.md) and follow its steps. |
| **Plan** | The approach warrants writing down before implementing — to survey patterns, align with the user, or survive a fresh session. Fits a single implementation session and touches one or two related subsystems. Produces a plan file. | Read [references/plan-mode.md](references/plan-mode.md) and follow its steps. |
| **Spec** | Spans multiple subsystems, requires multiple implementation sessions, or has architectural decisions that need a spec-level discussion before planning begins. Produces a spec plus shells. | Read [references/spec-mode.md](references/spec-mode.md) and follow its steps. |

## Recommend and Confirm the Route

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

Then use `AskUserQuestion` to have the user set the final route. Offer the recommended mode first, marked "(Recommended)", alongside the other two modes; the auto-appended "Other" lets the user describe a different path.

Carry the confirmed route into its reference file from the table above and follow its steps.

## Rules

- Diff size, perceived task simplicity, and context window concerns are not reasons to skip the chosen mode's phases.