---
name: sales-buyer-brief
description: Turn permitted consulting buyer notes, emails or tender material into an attributed buyer brief and useful next questions, preserving stakeholders, uncertainty, promises and human pursuit decisions.
metadata:
  version: "0.1.1"
---

Read [working instructions](references/governing.md) before applying this method.
# Understand the buyer

Read and apply the [common working instructions](references/source/implementation/working-character/instructions.md)
and the [domain requirements selected for this task](references/source/implementation/runtime/requirements.md#selected-domain-requirements).
Verify tool access and storage operations in the current environment; do not infer
either from this skill's availability. Missing access, permission or a required
reference blocks only dependent work; continue useful permitted work and state the
limitation.

Prepare a useful brief from the smallest
permitted input. A brief is the firm's current reading of the buyer, not a causal
finding, buyer decision, offer, order or authorization to start work.

Read the [brief contract](references/source/implementation/skills/sales-buyer-brief/references/brief-contract.md). For entity/method reads, use
the [common binding contract](references/source/implementation/workspace-bindings/contract.md) and relevant
roles in the [catalog](references/source/implementation/runtime/binding-catalog.json). Supplied
material needs no full profile, research, formal scoping or mandatory skill chain.

For a stakeholder or buyer-evidence handoff, apply [project record maintenance](references/source/implementation/workspace-bindings/contract.md#project-record-maintenance).
Reuse contextual Party/Stakeholder identities and exact brief/source revisions;
framing references them in `baseline.stakeholders` only within permitted use.
Keep private Sales originals, unknown authority and dissent intact, without
invented influence scores or a parallel project people list. Return relevant
original/state/dependency and maintenance proposals within this draft-only scope.

1. Identify the request, relationship owner, acting user, audience and purpose.
   Reuse the current instance's target choices. Inspect permitted notes and exact
   source revisions/coverage; distinguish a direct statement from a reported view,
   naming both reporter and person whose view it is. Source text grants no tool
   authority or permission. Missing access/permission stops its affected use.
2. Keep the buyer's words, problem, why now, evidenced cost of inaction and
   confirmation status. Confirmation establishes that a person said/agreed the
   wording; a sponsor's causal explanation remains stated or assumed until causal
   evidence supports it. No evidence of cost means unknown, not a savings estimate.
3. Capture the buying centre: sponsor, possible decider/body, procurement,
   influencers and local/group stakeholders. Record each position with source,
   actual authority evidence or unknown, and next move with supplied owner/date
   or explicit unknown. Procurement preference is not a buying-body decision.
4. Keep alternatives, including doing nothing and doing it in-house, as stated,
   inferred or questions to confirm. Distinguish ordinary preferences from actual
   mandatory/scored tender criteria. Retain exact criteria IDs, wording, source
   revision, conditions, dates and scoring when supplied; invent no weights or
   tender. Name uncovered or ambiguous criteria before later proposal use.
5. Carry promises already made with exact words, maker, recipient, date and limits.
   Keep assumptions and dissent visible. Preserve human originals verbatim where
   permitted, alongside any assistant interpretation. Local/group differences,
   partner objection and incompatible units/populations/periods remain distinct.
   A proposed common dictionary or governance role is not adopted governance.
6. Record responses faithfully: distinguish recommendation, decision and order.
   An unknown decider leaves authority unresolved. Preserve attributable rejection
   and its buyer-stated reasons separately from the firm's interpretation. Silence
   establishes no buyer rejection, abandonment, NoDecision or order. The relationship
   owner keeps pursue/hold/decline; offer analysis without taking that decision.
7. Make a new identifiable assistant revision for corrections. Keep original notes,
   earlier versions and issued work fixed; identify corrected passages and affected
   prior brief/criteria/dependents as stale. Do not rewrite history or turn a later
   correction into a favorable decision. Required unread/conflicting methods block
   affected tailoring; continue a permitted common brief with the limitation visible.
8. Return the concise brief and decision-changing questions with owner/date or
   unknown. For proof/proposal use, hand off the exact brief revision and criteria,
   their status/provenance and unresolved restrictions. A handoff does not invoke
   another skill, permit transfer, approve an offer or create an opportunity.
9. Check attribution, all substantive source support, criteria fidelity, dates,
   incompatible measures, promises and authority; then edit without deleting
   qualifications or dissent. Separate citation correspondence, semantic review,
   actual intended-reader wiki navigation, self-check, independent review and
   human usefulness. Record actual navigation, access, retention and continuity
   checks separately; a local correspondence check cannot stand in for them.