Workflow keyword trigger collides with normal use of the word "workflow"

[rogadev]

First off - I love dynamic workflows. The feature itself is great and I'm already getting value out of it.

My one piece of friction is the keyword trigger. Using the bare word "workflow" as the activation keyword is a problem because "workflow" is an extremely common word I type all the time when I'm just describing things - "user workflow," "UI workflow," "action workflow," "explain the deployment workflow," etc. None of those are requests to spin up an orchestration run, but they collide with the trigger.

Right now the burden is on me to notice the rainbow highlight and actively cancel something I never asked for (alt+w, or backspace after the word). That's an opt-out model for a heavyweight, token-expensive action. I'd much rather it be opt-in.

Two ways to fix this, either would make me happy:

1. A slash command - /workflow. Deliberate, unambiguous, never fires by accident. This is what I instinctively reached for first.
2. A unique keyword that nobody types in normal English - something like claudeflow. If the design goal is a magic word in the prompt, make it a word I'd never otherwise write while describing a workflow.

The current setup documents three separate ways to suppress an accidental trigger, which to me is a sign the keyword choice itself is the issue.

To be clear, I know I can disable the keyword trigger entirely in /config. But then I lose the convenience for the times I do want it. The point is the trigger word shouldn't be a high-frequency common noun.

Thanks for the feature - just want the activation to stop stepping on normal language.