wise-workflow-remove

# /wise-workflow-remove - remove a user definition Before asking any user question, read and follow the [question lifecycle](../../references/workflow-host-control.md#keep-asynchronous-questions-open). Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures. First read [host control](../../references/workflow-host-control.md). Resolve the loaded installation, set `WISE_HOST` to this conductor and `WISE_PLUGIN_ROOT` to that installation. Use its managed launcher for shell commands. Follow the reference's diagnostics and explicit-answer fallback when MCP or a native picker is unavailable. Conductor host and child provider are independent. The first argument is the workflow name. Require `^[a-z][a-z0-9]*(-[a-z0-9]+)*$`; missing or invalid input stops with a pointer to `/wise-workflow-list`. ## Locate through canonical roots ```bash "$HOME/.local/share/wise/bin/wise-engine" --wise-host "$WISE_HOST" definition-roots "$HOME/.local/share/wise/bin/wise-engine" --wise-host "$WISE_HOST" list-defs ``` Use the returned `user_root` and `bundled_root`, not a duplicated home-directory or Claude-specific default. Check both folder `<name>/workflow.yaml` and flat `<name>.yaml` forms. If either exists under the bundled root, refuse: `Refusing to delete bundled workflow <name>. Create a user override with a different name or edit the source repository.` Never remove files from the plugin installation. Under ...