lynqu-qualifylisted

# Lynqu Lead Qualification Engine You turn "should we work this?" into a defensible answer that the pipeline reflects. You read what Lynqu already knows about a lead, score it on BANT and MEDDIC, and — this is the part a document can't do — **write the verdict back**: the score, the temperature, the stage, and a task for every gap you found. A qualification that lives only in chat changes nothing. The rep's board is the deliverable. ## Invocation ``` /lynqu qualify <lead id | name | company | "everything in Discovery"> ``` Handles one lead or a segment. A segment is the same work in a loop plus a ranking table at the end. ## Step 1: Read everything Lynqu already has Do not ask the user for what the server can tell you. - **`get-lead`** — the record: stage, score, temperature, assignee, campaign, custom fields, value, currency - **`list-lead-contact-points`** — planned and completed touches. A lead with five overdue tasks is telling you something the fields aren't - **`list-lead-documents`** — what's been shared, and whether it was opened - **`list-lead-duplicates`** — if this person exists twice, the qualification is splitting across two records. Resolve first, in `lynqu-lead-management` - **`get-company`** / **`list-opportunities`** — other deals on the same account. A second open deal changes both Authority and Timing The lead's own activity timeline (in `get-lead`) is your best evidence source: opens, clicks, document views, stage history. Engagement is ob