cs-tool-selection
/cs-tool-selection
Purpose
/cs-tool-selection produces a selection framework — not a recommendation. It generates the evaluation criteria, the RFP question template, and the weighted shortlist rubric that a CS organization uses to run its own tool selection. The skill is pure framework, vendor-neutral by construction: no vendor names appear in the output. The buyer supplies the vendor list, runs the RFP, fills the rubric, and owns the choice.
This skill is deliberately downstream of /cs-segmentation-model and /health-score-design. The segmentation output determines which tool archetype is appropriate (enterprise CSP vs. product-analytics-led pooled tooling vs. hybrid); the health-score model determines where scores must originate and where they must be consumed. Skipping either input produces generic selection criteria that map to no real operating model — the common failure mode this skill is designed to avoid.
When to Use
Invoke /cs-tool-selection when you need to:
- Run a greenfield tool selection for a CS function being stood up for the first time
- Execute a tool consolidation when the current stack has drifted into overlapping capabilities
- Structure a contract renewal negotiation where the incumbent is the default but should be challenged
- Rationalize the stack after an M&A event that combined two CS organizations with different tooling
- Respond to a segmentation shift that invalidates the previous tool selection (e.g., enterprise book pivots to PLG)