prepare-discoverylisted

# Prepare Discovery Prepare a conversation that helps both sides determine whether change is worthwhile. Discovery is not a disguised product demo. ## Inputs Read `.agents/gtm-context.md`, the account brief, prior messages, and meeting details when available. Separate what is known from what needs validation. ## Build The Plan 1. Define the decision this call should enable. 2. Create up to three account or problem hypotheses, each tied to evidence. 3. Map the attendees and likely concerns without assuming authority. 4. Prepare a short agenda and permission-based opening. 5. Select questions that move from current state to impact, desired outcome, decision process, and next step. 6. Add follow-up prompts that ask for examples, frequency, consequence, and ownership. 7. Plan what not to ask because it is already public, answered, irrelevant, or premature. 8. Define a useful close: recap, gaps, and a possible next step. Keep proposed ownership and timing distinct from what the buyer accepts. 9. Before the call, require the responsible meeting owner to confirm the objective, actual attendees and roles, and material account facts or mark them Unknown. Record what changed; an unverified invite or public signal is not approval to personalize more strongly. Use [the discovery plan template](assets/discovery-plan.md). ## Question Quality Prefer: - "Walk me through the last time this happened." - "What does that delay affect downstream?" - "Who else experiences the problem diff