tritonkit-plan-arbiter

Compares competing implementation plans and selects one executable decision for TritonKit work.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-plan-arbiter-neptunekit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tritonkit-plan-arbiter
Source: https://github.com/NeptuneKit/TritonKit/tree/main/.agents/skills/tritonkit-plan-arbiter
Command: npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-plan-arbiter-neptunekit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple agents, PRs, or proposals offer competing implementation directions for TritonKit work, this Skill resolves the conflict into a single executable decision instead of a vague compromise. ## Core Features & Use Cases - Plan Normalization: Extracts goals, assumptions, touched files, validation gates, risks, and costs from each candidate plan before judging. - Structured Arbitration: Applies a fixed priority order (user requirements, product boundaries, real evidence, rollback safety, verification clarity, conflict surface, cost) to reach an Adopt, Hybrid, or Revise-first verdict. - Decision Memo Output: Produces a short memo covering the decision, rationale, execution steps, borrowed elements, rejected points, verification gates, and executor assignment. - Use Case: Two subagents propose different approaches for a TritonKit CLI feature; use this Skill to compare both against real repo files and schemas, then receive one clear execution plan with explicit verification steps. ## Quick Start Ask the agent to compare the attached Plan A and Plan B for the TritonKit issue and decide which one to execute.

Frequently Asked Questions about tritonkit-plan-arbiter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between multiple implementation plans from different agents?▼

Normalize each plan by extracting its goals, assumptions, touched files, validation gates, risks, and costs, then compare them against real repository evidence and product boundaries. The Skill outputs an Adopt, Hybrid, or Revise-first decision with a concrete execution plan.

What decision outcomes does plan arbitration produce?▼

Arbitration produces exactly one of three outcomes: Adopt (take one plan largely as-is), Hybrid (combine specific borrowed parts into a new execution sequence), or Revise first (all plans lack key facts or violate boundaries and must be rewritten).

When should I not use plan arbitration?▼

Do not use it when there is only one direct, low-risk plan that the user has already explicitly accepted. Arbitration is designed for genuine conflicts between two or more competing directions, not for confirming an agreed approach.

What evidence does plan comparison rely on?▼

Comparison prioritizes original sources over summaries: user requirements, plan texts, PRs, branches, subagent reports, real files, schemas, tests, screenshots, CI results, and official documentation. Unresolvable sources are listed as risks rather than blocking the decision.

What happens after a plan arbitration decision is made?▼

If the user has authorized execution, work proceeds according to the decision memo's execution plan and verification gates. Otherwise the process stops at the decision memo and waits for user confirmation before any implementation begins.