definitive-version git:20261107.665a973A

Immutable. This exact content never changes and is served at /api/v1/blob/68a7bef730eddcc5.

---
name: definitive-version
description: Choose between two definitive execution plans and return the winner, a brief reason, and material compatible ideas to borrow. Use for selection without a new plan or detailed comparison.
metadata:
  origin: custom
---

# Definitive Version

Choose the stronger of two definitive plans, read-only. Do not edit plans, write a third plan, or run checks that write artifacts or change external state. Keep selection state in context.

Read and apply [Plan standards](../write-plan/references/plan-standards.md) and [Resolve plan requirements](../write-plan/references/requirements.md).

## Inputs

Use exactly two distinct explicit paths to readable regular text files; ask for corrections instead of substituting files. Without paths, inspect only direct children of `.local/` at the repository root and find exactly two definitive plans for the same task by content and context. Ask for paths if the pair is not unique. Read both fully.

Establish the requirements from conversation context, or reconcile stored requirements and digests by meaning and provenance; identical wording, copied update histories, and missing originals are not blockers when intent is clear. Ask narrowly only about material unresolved scope or authority. For factual uncertainty, make a conditional selection.

## Select

Assess both plans against the same requirements: factual support, completeness including shared omissions, contradictions, risks, dependencies, prioritization, acceptance, executability without chat history or unstated decisions, and conformance with the execution contract. Flag missing checkpoint provisions and unsupported session breaks or confirmation handoffs, including shared ones. Consider material safe cleanup in the directly affected scope; do not invent work.

Verify disagreements that affect the choice against current evidence, and reconcile scope, version, date, assumptions, and behavior. Agreement is not proof. You can delegate independent read-only evidence questions under [Subagent roles and reasoning](../execute-plan/references/subagent-reasoning.md); reconcile the results before you choose. When evidence is limited, choose under explicit assumptions and state the check or condition that would reverse the choice.

Choose the strongest overall plan, not the one with the most isolated wins. Shared omissions can leave both plans unready to execute. Borrow only independently supported, material ideas that fit the winner and the requirements.

## Response

Lead with a clickable absolute path to the winner and one brief reason. Add borrow or adapt bullets only for useful changes. Disclose high-risk recommendations with reasons, mitigations, and residual risks, and material selection conditions or execution caveats. Selection does not grant execution authority. Omit praise, repeated requirements, scorecards, detailed comparison, and process narration.