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).
Allowed Tools
No tools specified
Provided by Plugin
hyperflow
Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist reviewer and investigator agents, adaptive depth so a 5-line fix never triggers a deep run, and persistent per-project memory that lives in your repo and never leaves it. Runs on whatever model your session already uses — zero config, no API keys, no daemon. Works across Claude Code, Codex App/CLI, OpenCode, Grok, Antigravity, and Cursor.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick 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
- Read the requested mode (on / auto / off).
- Write it to
.hyperflow/.sticky-mode(one word). - The core
hyperflowskill reads this on each task to decide whether to auto-route. - Print the new mode.
Rules
- This only changes routing behavior — it never runs work. Default is
autowhen the file is absent.