---
name: decision-brief
description: Prepare a concise evidence-based recommendation for a technical choice. Use when the user needs to choose an approach, not when an already confirmed decision merely needs execution.
---

# Decision brief

Help the user decide the simplest complete approach to the stated technical problem. Advice is not execution permission.

## Define the decision

Start from the stated outcome, constraints and settled decisions. Inspect authorized current sources before explaining the existing system. Identify the one unresolved choice that changes the next action; ask only when the user must supply it.

**Done when** the decision and its relevant constraints are explicit, without reopening settled choices.

## Compare what matters

Check existing native/platform means first. Recommend one complete approach and justify it with observed facts. Include an alternative only when it changes a material cost, risk, behavior or ownership boundary. Mark assumptions and missing evidence rather than inventing certainty.

**Done when** the recommendation can be traced to the goal, evidence and real trade-off.

## Deliver the brief

Return the recommended choice, short reasoning, material consequences and the next decision/action. For a small choice use a few sentences, not a dossier. Preserve authority and actual access/publication boundaries; do not install, edit or launch anything from an advisory task.

**Done when** the user can make an informed decision and knows any blocking uncertainty. If no new structure is needed, say so.
