triad-dispatch

Repair agent for the Antigravity (agy) dispatch wrapper (antigravity_wrapper.py) failures the dispatch SKILL routes to repair: classification `unknown` (a classifier gap), or `extraction-error` / `timeout` (rc-based failures routed here so this agent can decide whether a vendor pattern is worth a classifier patch or should escalate). Invoked ONLY by name from the dispatch SKILL — never auto-delegated. Input: a run-log file path in the prompt body (read via Read tool) containing exit_code, stderr, stdout, wrapper_cmd, and the failing call's full context. Purpose: progressively improve the engine's classification framework so future calls auto-route correctly without your dispatch — success metric = framework completeness, not fixing the immediate call. Patches the user classifier extension JSON `~/.config/triad-dispatch/classifier-patches.json` (the engine merges it at runtime), then re-runs with `--repair-mode` to verify routing. 3-attempt ceiling, then escalate.

Repair agent for the Codex dispatch wrapper (codex_wrapper.py) failures the dispatch SKILL routes to repair: classification `unknown` (a classifier gap), or `extraction-error` / `timeout` (rc-based failures routed here so this agent can decide whether a vendor pattern is worth a classifier patch or should escalate). Invoked ONLY by name from the dispatch SKILL — never auto-delegated. Input: a run-log file path in the prompt body (read via Read tool) containing exit_code, stderr, stdout, wrapper_cmd, and the failing call's full context. Purpose: progressively improve the engine's classification framework so future calls auto-route correctly without your dispatch — success metric = framework completeness, not fixing the immediate call. Patches the user classifier extension JSON `~/.config/triad-dispatch/classifier-patches.json` (the engine merges it at runtime), then re-runs with `--repair-mode` to verify routing. 3-attempt ceiling, then escalate.

Repair agent for the Gemini dispatch wrapper (gemini_wrapper.py) failures the dispatch SKILL routes to repair: classification `unknown` (a classifier gap), or `extraction-error` / `timeout` (rc-based failures routed here so this agent can decide whether a vendor pattern is worth a classifier patch or should escalate). Invoked ONLY by name from the dispatch SKILL — never auto-delegated. Input: a run-log file path in the prompt body (read via Read tool) containing exit_code, stderr, stdout, wrapper_cmd, and the failing call's full context. Purpose: progressively improve the engine's classification framework so future calls auto-route correctly without your dispatch — success metric = framework completeness, not fixing the immediate call. Patches the user classifier extension JSON `~/.config/triad-dispatch/classifier-patches.json` (the engine merges it at runtime), then re-runs with `--repair-mode` to verify routing. 3-attempt ceiling, then escalate.

3 CLI 에 한 질문을 동시에 던지고 답을 raw + 요약으로 받는 SKILL.

Use when the leader (Triad orchestrator) needs to dispatch a single-shot Antigravity CLI (`agy`) call via the wrapper framework. Triggering signals — leader is about to run `python3 antigravity_wrapper.py` raw; user said "agy 한 번 불러줘" / "antigravity로 X 처리" / "agy CLI 단발 실행" / "안티그래비티 호출"; a higher-level orchestration SKILL needs the agy leg of a fan-out (gemini CLI successor; gemini public EOL 2026-06-18, but 사내 keeps gemini until ~2026-07-31 so both ship in the interim); classification-aware routing with self-improving repair-agent fallback is needed instead of raw subprocess. Symptoms of skipping this SKILL — unknown classification failures don't reach the repair sub-agent, run-log files accumulate uncleaned, the framework's self-improving classifier never grows. Do NOT use for Codex (use `triad-codex-dispatch`), Gemini (use `triad-gemini-dispatch`), multi-turn dialogue / pair-coding (use `triad-pair-brainstorm` or `triad-pair-plan`), or 3-CLI fact-check fan-out (use `triad-3way-question`).

Use when the leader (Triad orchestrator) needs to dispatch a single-shot Codex CLI call via the wrapper framework. Triggering signals — leader is about to run `python3 codex_wrapper.py` raw; user said "codex 한 번 불러줘" / "codex로 X 처리" / "codex CLI 단발 실행" / "코덱스 호출"; a higher-level orchestration SKILL needs the Codex leg of a fan-out; classification-aware routing with self-improving repair-agent fallback is needed instead of raw subprocess. Symptoms of skipping this SKILL — unknown classification failures don't reach the repair sub-agent, run-log files accumulate uncleaned, the framework's self-improving classifier never grows. Do NOT use for Gemini (use `triad-gemini-dispatch`), multi-turn dialogue / pair-coding (use `triad-pair-brainstorm` or `triad-pair-plan`), or 3-CLI fact-check fan-out (use `triad-3way-question`).

Use for the FINAL pre-merge (or review-worthy / security-or-correctness-critical) cross-family review mandated by self-rule

Use when the leader (Triad orchestrator) needs to dispatch a single-shot Gemini CLI call via the wrapper framework. Triggering signals — leader is about to run `python3 gemini_wrapper.py` raw; user said "gemini 한 번 불러줘" / "gemini로 X 처리" / "gemini CLI 단발 실행" / "제미나이 호출"; a higher-level orchestration SKILL needs the Gemini leg of a fan-out; classification-aware routing with self-improving repair-agent fallback is needed instead of raw subprocess. Symptoms of skipping this SKILL — unknown classification failures don't reach the repair sub-agent, run-log files accumulate uncleaned, the framework's self-improving classifier never grows. Do NOT use for Codex (use `triad-codex-dispatch`), multi-turn dialogue / pair-coding (use `triad-pair-brainstorm` or `triad-pair-plan`), or 3-CLI fact-check fan-out (use `triad-3way-question`).