Mengorkestrasi keterlibatan multi-stakeholder dalam komite pembelian perusahaan untuk mencegah kegagalan kesepakatan akibat ketergantungan pada satu pihak saja.
- Bintang GitHub
- 79
- File
- 3
- Commit terakhir
- 14 Okt 2026
- Lisensi
- MIT
- Tool yang diizinkan
- —
Apa fungsi skill multi-thread-orchestration?
multi-thread-orchestration adalah agent skill. Mengorkestrasi keterlibatan multi-stakeholder dalam komite pembelian perusahaan untuk mencegah kegagalan kesepakatan akibat ketergantungan pada satu pihak saja.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill multi-thread-orchestration
Skill ini memungkinkan Anda mengelola siklus penjualan enterprise yang kompleks dengan melibatkan banyak stakeholder. Ini membantu para profesional sales untuk bergerak melampaui single-threaded deals, di mana satu titik kegagalan—seperti kehilangan champion utama—dapat membahayakan seluruh kontrak. Dengan memetakan buying committee dan mengidentifikasi peran yang hilang, Anda dapat membangun konsensus organisasi dan mencegah kesepakatan terhenti.
Seorang agent harus memuat tool ini saat pengguna perlu memetakan buying committee, mendeteksi ghost nodes, atau merancang strategi engagement paralel. Tool ini menghasilkan artefak konkret termasuk stakeholder maps, rencana engagement per peran, log deteksi ghost node, dan scorecard kesehatan kesepakatan. Skill ini menerapkan metodologi yang sudah mapan seperti MEDDICC, Gartner Challenger Sale, dan ITSMA untuk memastikan rekomendasi didasarkan pada framework penjualan yang terbukti. Skill ini dirancang untuk bekerja di berbagai lingkungan termasuk Claude Code, Cursor, dan Windsurf.
Apa yang bisa dilakukan agent dengannya
- 1Map a buying committeeIdentifikasi ketujuh peran kunci dalam akun enterprise untuk memastikan cakupan yang komprehensif.
- 2Detect missing stakeholdersTemukan pengambil keputusan tersembunyi, yang dikenal sebagai ghost nodes, yang berpotensi menghambat kesepakatan.
- 3Assess deal risk levelsHitung skor kesehatan berdasarkan berapa banyak stakeholder yang saat ini terlibat dalam proses tersebut.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill multi-thread-orchestration
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill multi-thread-orchestration di Claude Code
~/.claude/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.claude/skills/multi-thread-orchestrationInstall skill multi-thread-orchestration di Claude Code (project)
.claude/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration .claude/skills/multi-thread-orchestrationInstall skill multi-thread-orchestration di Codex
~/.agents/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.agents/skills/multi-thread-orchestrationInstall skill multi-thread-orchestration di Gemini CLI
~/.gemini/skills/multi-thread-orchestration/SKILL.md
$ npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.gemini/skills/multi-thread-orchestrationInstall skill multi-thread-orchestration di 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
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Lolos cek otomatis kami. Ini bukan audit keamanan: baca skripnya sebelum membiarkan agent menjalankannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauleadmagic/gtm-skills/skills/abm/multi-thread-orchestration is public and reachablegithub.com/leadmagic/gtm-skills/tree/HEAD/skills/abm/multi-t ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-10-14github.com/leadmagic/gtm-skills/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensial1 script read; no download-and-run, remote eval, base64 execution or credential uploadLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/leadmagic/gtm-skills/blob/HEAD/skills/abm/multi-t ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/leadmagic/gtm-skills/blob/HEAD/skills/abm/multi-t ↗Lolos
- SKILL.md mengikuti format Agent SkillsValid name and description; says when to use it; 162 linesgithub.com/leadmagic/gtm-skills/blob/HEAD/skills/abm/multi-t ↗Lolos
SKILL.md
Lihat di 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
Berkas dalam skill ini
3Pertanyaan seputar skill multi-thread-orchestration
Bagaimana cara install skill multi-thread-orchestration di Claude Code?
Jalankan npx degit LeadMagic/gtm-skills/skills/abm/multi-thread-orchestration ~/.claude/skills/multi-thread-orchestration. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill multi-thread-orchestration?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.
Apa itu ghost nodes dalam sebuah kesepakatan penjualan?
Ghost nodes adalah stakeholder yang tidak teridentifikasi namun memiliki kekuatan untuk menunda atau membatalkan kesepakatan, seperti perwakilan dari bagian legal, security, atau finance.
Bagaimana cara saya menilai kesehatan sebuah kesepakatan menggunakan skill ini?
Anda dapat menggunakan scorecard kesehatan kesepakatan dengan skala 0-100 berdasarkan cakupan thread, di mana keterlibatan kurang dari 3 stakeholder dianggap berisiko tinggi.
Konten spesifik apa yang harus dikirimkan kepada Technical Buyer?
Technical buyer sebaiknya menerima diagram arsitektur, security whitepapers, dokumentasi API, atau laporan SOC2.