ask-ailisted

# Ask AI ## Overview Coordinate one useful external-AI result without treating providers as interchangeable or replacing work Codex and local owners can complete directly. Ask AI owns authorization, request packaging, basis identity, operation idempotency, response attribution, and local verification. Provider references own only their verified product surfaces, capabilities, route requirements, and completion evidence. Package-only preparation and explicit manual user relay are portable; direct external collaboration requires a verified provider-specific host operation or browser route. Legacy requests that explicitly say ask-chatgpt route here with provider ChatGPT; do not maintain a second public collaboration owner. ## Workflow 1. Read effective guidance and normalize the request into outcome, provider set, subject, known facts, decision or review basis, constraints, exclusions, evidence needs, workflow, requested rounds or turns, and stop condition. Ask only when a missing choice would materially change the external recipient or result. 2. Apply the **Codex-first gate**. If Codex, an existing Skill, or an available host tool can produce the requested result and the user did not request an independent external-AI result or artifact, route there and stop. 3. Resolve an exact user-defined instruction alias when present, then providers, with [provider-routing.md](references/provider-routing.md). A user-named provider is a hard recipient constraint.