v6.0.0

Major release: cost-aware subagent model routing, guided onboarding, configurable commit strategy, and bounded parallel dispatch.

Subagent Model Routing (opt-in)

Plan execution no longer sends every subagent to the session model. Each plan task carries a modelTier (mechanical / standard / frontier), and implementers, reviewers, and fix dispatches run on the cheapest model that fits the work. On frontier-priced sessions this routes the bulk of plan execution to Haiku/Sonnet while judgment work keeps full power.

• One-file opt-in: docs/superpowers/model-routing.json in your project, or ~/.claude/superpowers/model-routing.json as a user-level default (project file wins). Delete the file to switch everything off.
• Four harness-enforced layers, all dormant without the routing file: a session-start notice that injects the tier rules, a plan gate requiring a valid tier on every plan task, a dispatch gate validating each Agent call against the union of in-progress task tiers, and an execution-handoff guard. Kill switch: SUPERPOWERS_ROUTING_GUARD=0. Everything fails open on parse errors.
• Tiers are abstract on purpose: plans survive model generations; the routing file decides what a tier means today. A concrete model pin in task metadata overrides the tier.
• Design doc: docs/model-routing-flow.md (including what this deliberately does NOT do: no token budgets, no spend telemetry).

Guided Onboarding

New /superpowers-extended-cc:onboard command: a short multiple-choice walkthrough of the optional features (model routing, user-gate enforcement hooks, commit strategy) that writes the chosen configuration files in place. One scope choice, asked once, governs every write: this project (docs/superpowers/ plus the project's .claude/settings.json) or user-level for all projects (~/.claude/superpowers/ plus ~/.claude/settings.json), with each write confirmed back with its absolute path. Manual setup stays fully documented in the README; onboarding is a convenience, never a requirement.

Commit Strategy (opt-in)

docs/superpowers/workflow.json with {"commitStrategy": "at-end"} switches plan execution from per-task commits to a single commit at plan end: tasks leave changes in the working tree and one final task commits the full implementation. Default behavior (per-task commits) is unchanged when the file is absent. Design doc: docs/workflow-config-flow.md.

Bounded Parallel Dispatch

subagent-driven-development now permits concurrent subagents instead of forbidding all parallelism: read-only audit and verification agents are always parallel-safe, and implementers may run concurrently when their tasks' files lists are disjoint and their blockedBy chains are independent. Two writers on one file remain forbidden, and every task keeps its own two-stage review. The dispatch gate understands multiple in-progress tasks and validates against the union of their tiers.

Plan Quality

• The plan document header gains a "User decisions (already made)" record, and deferred decisions must be self-contained when they fire: the question names the artifact with its role and verified state, says why it is still open, and may never recommend against a recorded decision.
• During execution, coordinators answer questions from the plan record first and only escalate to you when the record genuinely does not answer them.

Model routing is documented for Claude Code v2.1.170 and later.