triaging-requestslisted

# Triaging-Requests — The entry gate of every session **This skill classifies and dispatches. It does not plan, implement, or review.** Announce at start (pt-br): "Analisando o pedido para escolher a cerimônia certa." All identifiers and reasoning stay in English. Every message to the operator is **pt-br, product-language**. --- ## Execution mode — interactive vs headless Detect the mode **first**; it changes whether you may ask questions or wait for a human. - **INTERACTIVE (local):** an operator is present. Default. Clarifying questions and the human veto (Step 4) are available. - **HEADLESS (cloud routine):** no operator is reachable. Active when the session is a cloud routine (env `$CLAUDE_CODE_REMOTE` is set / `claude-code-on-the-web`) **or** the trigger prompt explicitly says to run autonomously. Confirm with a quick `echo "$CLAUDE_CODE_REMOTE"` if unsure. In **HEADLESS** mode the golden rules apply (see the root `CLAUDE.md`): never `AskUserQuestion`, never plan-mode, never wait for a human. Steps 2 and 4 below have an explicit headless branch. --- ## Pipeline ### Step 1 — Is this a dev/build task? Ask: does the request require writing, changing, or deleting code or configuration? **If NO** (question, chat, clarification, reading, review of a document) → **no ceremony**. Answer directly and stop here. Do not force a pipeline onto a conversation. **If YES** → continue to Step 2. --- ### Step 2 — Classify: QUICK / LIGHT / FULL **INTERACTIVE:** classify on