[docs] Stage-bundles design doc v1：SPIN 缺口板與階段教練（#137，先討論再實作） - #144
Merged
Merged
Conversation
Part of #137. Proposes the full sales-pipeline workflow as data-driven StageBundles: gap board as a claim-base projection (slots with ghost rows), click-to-ask question suggestions riding the SolutionReply pattern, and in-call coach rules (next-step gatekeeper, premature pricing, SPIN-order quality, per-stage talk ratio) riding the existing eval engine the same way red-line guards do. S1-S12 proposal decisions + open questions for review; appendix maps every concept to the existing mechanism it reuses. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
This was referenced Jul 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #137 —— stage-bundle 工作流的 design doc v1，先討論再實作：S1–S12 是提案不是定案，§10 列了 7 個要你拍板的問題。
核心設計一句話
每個階段一個 StageBundle（缺口板 slots＋教練規則＋退出條件＋預設時長），資料驅動；板是 claim base 的投影不是新儲存——slot 掛卡、空/薄/實由卡算出，幽靈列就是負空間。
幾個關鍵取捨（review 重點）
Claim加 optionalslotIds。stagecoach:前綴），本地型（talk-ratio、守門員計時、空檔偵測）走 delivery monitor。附錄 A 有完整 reuse 對應表。分期提案
P1 作戰室板＋建議問法（無 live 依賴）→ P2 live 板＋守門員/過早報價/talk-ratio → P3 SPIN 順序品質＋Settings 編輯器＋org 鋪路。若你要 live-first，§10-6 有對調的代價評估。
另外把 mini-crm.md §8 的「另開 design doc」改成指向本文件。
🤖 Generated with Claude Code