Orchestre l'engagement des multiples parties prenantes au sein des comités d'achat en entreprise pour éviter l'échec d'une transaction due à un interlocuteur unique.
- Étoiles GitHub
- 79
- Fichiers
- 3
- Dernier commit
- 14 oct. 2026
- Licence
- MIT
- Outils autorisés
- —
Que fait la skill multi-thread-orchestration ?
Orchestre l'engagement des multiples parties prenantes au sein des comités d'achat en entreprise pour éviter l'échec d'une transaction due à un interlocuteur unique.
Résumé généré à partir du SKILL.md de la skill.
À propos du skill multi-thread-orchestration
Cette compétence permet de gérer des cycles de vente complexes en entreprise en engageant de multiples parties prenantes. Elle aide les professionnels de la vente à dépasser le stade des transactions à interlocuteur unique, où un seul point de défaillance, comme le départ d'un champion, pourrait compromettre l'intégralité du contrat. En cartographiant le comité d'achat et en identifiant les rôles manquants, les utilisateurs peuvent instaurer un consensus organisationnel et éviter que les transactions ne stagnent.
Un agent doit charger cet outil lorsqu'un utilisateur a besoin de cartographier un comité d'achat, de détecter des ghost nodes ou de concevoir des stratégies d'engagement parallèles. Il produit des artefacts concrets, notamment des cartes des parties prenantes, des plans d'engagement par rôle, des journaux de détection de ghost nodes et des scores de santé de transaction. Le SKILL applique des méthodologies établies telles que MEDDICC, Gartner Challenger Sale et ITSMA pour garantir que les recommandations s'appuient sur des cadres de vente éprouvés. Il est conçu pour fonctionner dans divers environnements, notamment Claude Code, Cursor et Windsurf.
Ce qu'un agent peut faire avec
- 1Cartographier un comité d'achatIdentifier les sept rôles clés au sein d'un compte entreprise pour assurer une couverture complète.
- 2Détecter les parties prenantes manquantesTrouver les décideurs cachés, appelés ghost nodes, qui pourraient potentiellement bloquer une transaction.
- 3Évaluer les niveaux de risque d'une transactionCalculer un score de santé basé sur le nombre de parties prenantes actuellement engagées dans le processus.
Rédigé à partir du SKILL.md du skill. Chaque cas d'utilisation est vérifié par rapport à une citation de celui-ci.
Comment installer la skill multi-thread-orchestration
Chaque commande copie le dossier de la skill dans le répertoire des skills du client. Redémarrez le client ou démarrez une nouvelle session pour la charger.Installer la skill multi-thread-orchestration dans Claude Code
~/.claude/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.claude/skills/multi-thread-orchestrationInstaller la skill multi-thread-orchestration dans Claude Code (project)
.claude/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration .claude/skills/multi-thread-orchestrationInstaller la skill multi-thread-orchestration dans Codex
~/.agents/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.agents/skills/multi-thread-orchestrationInstaller la skill multi-thread-orchestration dans Gemini CLI
~/.gemini/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.gemini/skills/multi-thread-orchestrationInstaller la skill multi-thread-orchestration dans Claude.ai
npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration multi-thread-orchestration && zip -r multi-thread-orchestration.zip multi-thread-orchestration # claude.ai → Customize → Skills → + → Create skill → Upload a skill → multi-thread-orchestration.zip
Vérifications automatisées
Exécuté le 15 nov. 2026Rapport complet →A réussi nos vérifications automatiques. Ce n'est pas un audit de sécurité : lisez les scripts avant de laisser un agent les exécuter. Fonctionnement des vérifications
- Dépôt source lié et accessibleleadmagic/gtm-skills/skills/abm/multi-thread-orchestration is public and reachablegithub.com/leadmagic/gtm-skills/tree/HEAD/skills/abm/multi-t ↗Réussi
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit 2026-10-14github.com/leadmagic/gtm-skills/commits ↗Réussi
- Aucun téléchargement-exécution ni vol d'identifiants dans les scripts1 script read; no download-and-run, remote eval, base64 execution or credential uploadRéussi
- Aucune instruction cachée dans SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/leadmagic/gtm-skills/blob/HEAD/skills/abm/multi-t ↗Réussi
- Les outils préautorisés sont limitésNo pre-approved tools; the agent asks before using onegithub.com/leadmagic/gtm-skills/blob/HEAD/skills/abm/multi-t ↗Réussi
- SKILL.md respecte le format Agent SkillsValid name and description; says when to use it; 162 linesgithub.com/leadmagic/gtm-skills/blob/HEAD/skills/abm/multi-t ↗Réussi
SKILL.md
Voir sur GitHubMulti-Thread Orchestration
Overview
Single-threaded deals die when the champion leaves or loses internal support. Multi-threading means engaging multiple stakeholders in the buying committee with role-relevant messaging — so the deal survives any individual departure and builds organizational consensus. This is an enterprise sales superpower.
Authoritative Foundations
- Andy Whyte — MEDDICC Champion & Economic Buyer — Qualification scorecard — Metrics, Economic buyer, Decision criteria, Champion, Competition.
- Force Management MEDDICC Methodology — Command of the Message — persona-specific value narrative and differentiation per stakeholder.
- Gartner Challenger Sale Stakeholder Mapping — Teach-tailor-take control — reframe buyer thinking with insight-led conversations.
- ITSMA — Account-Based Marketing — Tier-based ABM (1:1 / 1:few / 1:many); measure pipeline from target accounts, not lead volume.
When to Use
- "Multi-thread this deal"
- "Map the buying committee"
- "Who else should we be talking to?"
- "Deal is stuck with one contact"
Core Principle
The biggest risk to any enterprise deal is not the competitor — it's "no decision." No decision happens when your champion can't sell internally as well as you sell externally. Multi-threading arms them with the right message for every stakeholder.
Step-by-Step Process
Phase 1: Stakeholder Identification
Map all 7 roles in the buying committee:
- Executive Sponsor: EVP/C-level. Controls budget. Cares about strategic impact.
- Champion: Day-to-day contact. Sells internally. Cares about career advancement.
- Economic Buyer: Signs the check. Cares about ROI, risk, and timeline.
- Technical Buyer: IT/Security/Architecture. Cares about implementation, security, scale.
- Influencer: End user or adjacent team lead. Cares about workflow improvement.
- Blocker: Status quo defender. Cares about avoiding change/disruption.
- Coach: Internal ally (may not be obvious). Gives you intel on decision process.
Phase 2: Ghost Node Detection
"Ghost nodes" are stakeholders you haven't identified yet who can kill the deal. Detection triggers:
- "We're waiting on legal review" → Ghost node: General Counsel
- "IT needs to approve the security review" → Ghost node: CISO/VP Security
- "Finance is looking at the budget allocation" → Ghost node: CFO/VP Finance
- "We need procurement to finalize" → Ghost node: Procurement director
- Any new name that appears after deal stage 3
When you detect a ghost node: immediately request an intro, prepare role-specific content, and add them to your stakeholder map.
Phase 3: Role-Specific Engagement
Per stakeholder role, deliver:
- Exec Sponsor: 1-page executive summary, peer references, industry benchmarking
- Champion: Internal selling toolkit, ROI slide, competitor comparison, implementation plan
- Economic Buyer: Business case with conservative scenario, payback timeline, risk mitigation
- Technical Buyer: Architecture diagram, security whitepaper, API docs, SOC2 report
- Influencer: Use case demo, workflow integration walkthrough, training outline
- Blocker: Risk acknowledgment, transition plan, vendor stability proof
Phase 4: Parallel Play Design
Run simultaneous plays across threads:
- Champion gets enablement content Thursday morning
- Exec sponsor gets peer case study Thursday afternoon
- Technical buyer gets security review response Friday
- All converge at next week's steering committee where your champion presents
Phase 5: Deal Health Scoring
Score 0-100 based on thread coverage:
- <3 stakeholders engaged: HIGH RISK (single point of failure)
- 3-4 stakeholders: MEDIUM RISK
- 5+ stakeholders with exec sponsor engaged: LOW RISK
- Ghost node detected and not engaged: CRITICAL RISK regardless of count
Output Format
Stakeholder map (power/interest grid), per-role engagement plan, ghost node detection log, parallel play timeline, and deal health scorecard.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- Treating ABM as a marketing-only initiative. ABM requires tight sales alignment. Without BDRs assigned to specific accounts and shared account briefs, marketing produces content nobody uses. Fix: weekly ABM standups with marketing + BDRs + AEs.
- One-size-fits-all tiering. Applying the same playbook to Tier 1 and Tier 3 accounts. Fix: Tier 1 gets custom content and executive engagement; Tier 3 gets automated personalization.
- Measuring ABM on MQLs. ABM success is pipeline from target accounts, not lead volume. Fix: track coverage %, engagement depth, pipeline created, and win rate by tier.
Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
Diagnostic Questions
- What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
- Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
- What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
- What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
- What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- Force Management MEDDICC: apply only the part that directly improves the requested deliverable.
- Gartner Challenger Sale Stakeholder Mapping: apply only the part that directly improves the requested deliverable.
- ITSMA — Account-Based Marketing: apply only the part that directly improves the requested deliverable.
Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
Execution Artifacts
references/framework-notes.md— Named frameworks and reference tablestemplates/output-template.md— Deliverable shell for agent outputscripts/check-output.py— Lightweight deliverable validator
Related Skills
- meeting-prep, objection-handling, abm-strategy, pipeline-management, demo-scripts
Fichiers de cette skill
3Questions sur la skill multi-thread-orchestration
Comment installer la skill multi-thread-orchestration dans Claude Code ?
Exécutez npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.claude/skills/multi-thread-orchestration. Claude Code charge les skills depuis ~/.claude/skills (tous les projets) ou .claude/skills (un seul projet) et utilise une skill lorsque sa description correspond à la tâche.
Quels clients peuvent utiliser la skill multi-thread-orchestration ?
Tout client qui lit le format Agent Skills : Claude Code, Codex, Gemini CLI et claude.ai (envoi sous forme de ZIP). Les scripts de la skill ne s'exécutent que si le client autorise l'exécution de code.
Que sont les ghost nodes dans une transaction commerciale ?
Les ghost nodes sont des parties prenantes non identifiées qui ont le pouvoir de bloquer ou d'annuler une transaction, comme des représentants des services juridiques, de la sécurité ou de la finance.
Comment puis-je évaluer la santé d'une transaction à l'aide de ce SKILL ?
Vous pouvez utiliser un score de santé de la transaction de 0 à 100 basé sur la couverture des interlocuteurs, où l'engagement de moins de 3 parties prenantes est considéré comme un risque élevé.
Quel contenu spécifique doit être envoyé à un acheteur technique ?
Les acheteurs techniques doivent recevoir des schémas d'architecture, des livres blancs sur la sécurité, de la documentation API ou des rapports SOC2.