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, 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 and follow its steps.
Plan	The approach warrants writing down before implementing — to survey patterns 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 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 and follow its steps.

turboplan