hyperflow-sticky

Hyperflow auto-routing mode. Use to control how aggressively hyperflow auto-routes — "make hyperflow sticky", "stop using hyperflow", "auto-route to hyperflow", "disable hyperflow auto-routing". Sets on (every task-shaped message routes) / auto (intent-verb messages route — default) / off (no auto-routing).

hyperflow Plugin
ai agency Category

Allowed Tools

No tools specified

Provided by Plugin

hyperflow

Fifteen specialized slash commands turn one Claude session into a structured multi-agent engineering pipeline. Thinking models orchestrate, triage, and review; worker models execute in parallel — every step is a Worker → Reviewer pair, and every non-trivial phase fans into sub-phases with their own reviewers. Auto-routing is on by default — say 'audit the diff', 'debug this test', 'large migration', or 'run a workflow' and the orchestrator routes to the right skill without the /hyperflow:* prefix. /hyperflow:workflow uses Claude Code dynamic workflows for big tasks and a portable Codex/OpenCode adapter where native workflows are unavailable; /hyperflow:spec asks the questions a senior engineer would; /hyperflow:scope decomposes into a batched task graph; /hyperflow:dispatch fans out persona-stitched workers under tiered review; /hyperflow:amplify rewrites a rough prompt into a high-quality one before you run it. 15 composable personas, 6 adaptive flow profiles, and persistent project memory compound across sessions. Works across Codex App/CLI, Claude Code, OpenCode, and Antigravity.

ai agency v4.26.1
View Plugin

Installation

This skill is included in the hyperflow plugin:

/plugin install hyperflow@claude-code-plugins-plus

Click to copy

Instructions

hyperflow-sticky — auto-routing mode (Antigravity single-agent)

Control hyperflow's auto-routing aggressiveness. Follow the hyperflow doctrine.

Modes

  • on — every task-shaped message routes through a hyperflow workflow.
  • auto (default) — only messages whose first verb matches the routing table (build/fix/audit/scope/design/ship…) route.
  • off — no auto-routing; hyperflow runs only when a /hyperflow* command is explicitly invoked.

Steps

  1. Read the requested mode (on / auto / off).
  2. Write it to .hyperflow/.sticky-mode (one word).
  3. The core hyperflow skill reads this on each task to decide whether to auto-route.
  4. Print the new mode.

Rules

  • This only changes routing behavior — it never runs work. Default is auto when the file is absent.

Ready to use hyperflow?