Wheel Run

On success it prints a JSON object like:

{"name": "my-workflow", "step_count": 5, "activate_name": "my-workflow", "plugin_dir": "/path/to/plugin"}

Step 2: Activate

Run activate.sh as a separate, single-line Bash call using the activate_name and plugin_dir from Step 1's output. Substitute the actual literal values — no shell variables.

mkdir -p .wheel

Then:

<plugin_dir>/bin/activate.sh <activate_name>

The PostToolUse hook intercepts this call, reads the workflow file, creates the state file with proper ownership, and runs kickstart to advance through any automatic initial steps.

Step 3: Confirm

echo "Workflow started. Hooks are now active."
echo "Run /wheel-status to check progress, /wheel-stop to deactivate."

That's it. Do NOT read the state file or workflow file — the hooks will tell you what to do next.

Rules

• If $ARGUMENTS is empty, ask the user for a workflow name. List available workflows from workflows/*.json and installed plugins.
• Never create a state file directly — always go through activate.sh + hook.
• Plugin workflows are read-only (FR-030) — they execute from the plugin's install path. Users can copy to workflows/ to customize, and the local copy takes precedence.

Execution Behavior (NON-NEGOTIABLE)

After activation, all workflow progression happens through hooks. Do not manually advance the cursor, update step statuses, or modify state files yourself.

• Do NOT read the workflow JSON file. The validation script handles that. You don't need to know step details — hooks will instruct you.
• Do NOT read state files. Use /wheel-status if you need to check progress.
• Do NOT spawn sub-agents for any workflow step — including "type": "workflow" steps. Workflow steps are like function calls: the referenced workflow runs inline in the same conversation, dispatched by the hook system.
• Do NOT manually stop workflows. Use /wheel-stop and let the hook handle archival.
• Do NOT manually archive or delete state files. The hook system owns the workflow lifecycle.
• Your only job after activation is to execute the current step's work as instructed by hooks, and let hooks handle progression to the next step.