/**
 * `/workflows` and `/workflow <subcommand>` — read-only commands for browsing
 * saved workflows.
 *
 * Why only read commands here? Slash command results are sent to the user; they
 * are NOT injected back into the agent's turn. Triggering a workflow run from
 * the slash layer would require a non-trivial cross-cutting "inject this as the
 * next user message" hook that doesn't exist yet. Instead, the workflow tool
 * understands `name`, and its description tells the model to prefer that route
 * whenever a user mentions a saved workflow by name. Plain text — "run the
 * audit_repo workflow" — works end-to-end.
 *
 * `/workflows` and `/workflow view` make discovery cheap, which is the missing
 * piece.
 */
import type { CommandDefinition } from '../types.js';
export declare const workflowCommand: CommandDefinition;
export declare function registerWorkflowCommands(): void;