brieflisted

# /requivo:brief Write the **decision brief** — what someone needs to review with a client, a product lead or an engineering lead *before* estimating this request. A judgment, not a recap, and not a PRD. **You** do the analysis; Requivo tracks the document. Read `${CLAUDE_PLUGIN_ROOT}/REASONING.md` first. ## 0. Preflight Run the shared **preflight** from REASONING.md before anything else: `requivo doctor --json`, checking whether the command ran *at all* rather than what it reported. If it could not run, the `requivo` CLI is not installed — say the four things REASONING.md lists and stop. Nothing has been applied or saved at this point, so there is no half-written brief to find. ## 1. Check readiness, honestly ``` requivo status <slug> --json ``` Note the `revision` — call it `N`. It is the understanding this brief will rest on, and you will state it when you save. If high-impact topics are still unresolved, **say so up front**. A brief written on a thin understanding must flag its assumptions — never present an inferred topic or an open decision as settled. ## 2. Load the model ``` requivo model show <slug> requivo context --session <slug> # exactly the cards this session was created with ``` ## 3. Reason → write the brief Produce it in PM language, in the order a scope review is run: 1. **Request and objective** — the underlying problem, what is being built, complexity and its cost driver. 2. **Current understanding** — the scope in a short paragraph. 3. **What is