canonical-advisor-routinglisted

## Purpose Route a prompt through a local provider CLI and persist the result as an artifact. The execution path is process-first: always go through the canonical `apx ask-*` wrappers rather than hand-assembled raw provider commands, so routing and artifact capture stay consistent. ## When to Use - You want a focused second opinion, review, or plan from a local provider - You are about to invoke a provider CLI directly and want a consistent entry point - The response needs to be saved to disk for later reference, not just printed - A previous wrapper run misbehaved and you are debugging the routing ## Inputs - A clear prompt describing the task for the advisor - The chosen provider (codex, gemini, or claude) installed and authenticated locally ## Workflow 1. **Pick the provider and frame the prompt.** Choose `ask-codex`, `ask-gemini`, or `ask-claude` based on the task, and write a single self-contained prompt string. 2. **Invoke the canonical wrapper.** Run the prompt through the `apx ask-*` command. Do not manually assemble raw provider CLI commands unless you are debugging the wrapper itself. ```bash apx ask-codex "review this patch from a security perspective" apx ask-gemini "suggest UX improvements for this flow" apx ask-claude "draft an implementation plan for issue #123" ``` 3. **Confirm prerequisites if the call fails.** Verify the selected local CLI is installed and authenticated before retrying; a missing or unauthenticated CLI is the usual c