← ClaudeAtlas

trident-looplisted

Harden a plan with independent cross-provider review (Claude, Codex, Kimi, DeepSeek, Qwen, OpenCode), then optionally build and cross-inspect it. Start in any supported host CLI: the host plans and another provider reviews. Use for trident this plan, trident-loop, or trident this feature; not for trivial edits.
RogerioTrani/trident-loop · ★ 0 · Code & Development · score 62
Install: claude install-skill RogerioTrani/trident-loop
# Trident Loop The current conversation owns requirements, planning and coordination. The other provider reviews the plan. Either provider can build; the provider that did not build inspects the final code in a fresh session. ## Resolve roles once Identify the actual host from your runtime, not PATH, installed skills, model-name guesses, or the repository. Several CLIs may be installed. Any registered provider can be the host: use `host=claude` in Claude Code, `host=codex` in Codex, `host=kimi` in Kimi Code, and the matching runtime identity for any further provider. If the runtime identity is unavailable, ask which host the user is using once. **Provider registry and pipeline order.** The default pipeline order is the explicit list `claude, codex, kimi, deepseek, qwen, opencode`. A provider joins the end of the list once its runner boundary is implemented, and the order can be changed per run with `providers=` / `PROVIDER_ORDER`. Resolve every default role from this order: - Default plan reviewer: the first provider in the pipeline order that is not the host. - Default builder: the host. The host remains coordinator even when another provider builds. - Default final inspector: the first provider in the pipeline order that is not the builder, in a fresh session. Honor explicit `reviewer=`, `builder=` and `inspector=` with any registered provider. To swap the planner, start the conversation in the other host; do not pretend a CLI reviewer is the user's planning conversat