Turbocharge

When your Claude workflow is working but you need it to work faster, cheaper, or more reliably, this is what you reach for. It enforces a proposal-before-building flow where you explore 2-3 optimization directions with tradeoffs, then implement techniques like parallel fan-out, streaming pipelines, model cascading, or complexity-based routing. The mandatory rule is progressive enhancement: every turbocharge must degrade gracefully so the base workflow still functions if the optimization fails. Smart constraint here is refusing to optimize before correctness, which saves you from prematurely optimizing broken logic. Pair it with /evaluate afterward to verify both the performance gain and the graceful degradation.

skills.sh installs: 337
GitHub stars: 602
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add sharpdeveye/maestro --skill turbocharge --agent claude-code

Installs into .claude/skills of the current project.

Files

MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.

Start your response with:

──────────── ⚡ TURBOCHARGE ─────────────
》》》 Entering turbocharge mode...

Push a workflow past conventional limits. This isn't about adding features — it's about making existing capabilities operate at a level users didn't think was possible.

EXTRA IMPORTANT: Context determines what "extraordinary" means. Understand the project's scale before deciding what to turbocharge.

Propose Before Building

Think through 2-3 different directions with trade-offs
Present these options to the user and wait for their selection before writing code
Only proceed with the confirmed direction