sticky

Toggle auto-routing modes for task-shaped messages with intent detection.

3|Updated May 14, 2026
One-click install
npx skills add https://github.com/Mohammed-Abdelhady/hyperflow --skill sticky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sticky
Source: https://github.com/Mohammed-Abdelhady/hyperflow/tree/main/skills/sticky
Command: npx skills add https://github.com/Mohammed-Abdelhady/hyperflow --skill sticky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The sticky Skill unit solves the problem of controlling the auto-routing of task-shaped messages within a project, allowing users to easily toggle between on, auto, and off modes for auto-routing.

Core Features & Use Cases

  • Toggle Auto-Routing: Set auto-routing mode to on, auto, or off to control how task-shaped messages are routed.
  • Intent Detection: Default intent-detection for messages containing chain-starter verbs.
  • Subcommands: Use subcommands like on, auto, off, and status to manage and check the sticky mode.
  • State Persistence: Sticky state is stored in a .hyperflow/.sticky file, allowing persistence across sessions.

Quick Start

Use the /hyperflow:sticky on command to enable full sticky routing for task-shaped messages.

Frequently Asked Questions about sticky

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control auto-routing for task-shaped messages in a workflow?

Project workflow orchestration requires setting up task routing rules to define how task-shaped messages are distributed. Configuring these routing parameters ensures messages are directed to the correct processing stages.

How does intent detection work for messages with chain-starter verbs?

Intent detection for chain-starter verbs operates by analyzing message content to identify task initiation commands. Evaluating these verb triggers ensures proper routing of task-shaped messages within the workflow.

Can I persist auto-routing state across multiple project sessions?

Auto-routing state persists across sessions by storing the sticky mode configuration in a .hyperflow/.sticky file. Saving this state ensures routing preferences remain intact between project interactions.

Do I need additional dependencies to manage task routing modes?

Managing task routing modes requires no additional dependencies to function. Operating natively within the project environment allows workflow orchestration without installing external packages.

What is the difference between on, auto, and off routing modes?

The on mode enforces sticky routing for all task-shaped messages, auto applies default intent detection for chain-starter verbs, and off disables routing completely. Switching between these subcommands controls workflow orchestration behavior.