mcorbett51090/ravenclaude/technical-discovery
Claude Code and agent skill by mcorbett51090/ravenclaude
- community
Checking that the SKILL.md file is still in the repository.
Run value-based technical discovery before any demo or POC — frame the deal with MEDDPICC, surface the prospect's pain and its quantified business impact, identify the decision criteria/process/champion, and capture it all in the discovery-notes template so the demo can be tailored to real pain. Reach for this when the user has (or just had) a discovery call, or is about to demo with no discovered pain. Used by `sales-engineer` (primary) and `poc-evaluation-lead`.
Install
npx vskill@latest install mcorbett51090/ravenclaude/technical-discoverySKILL.md
The same SKILL.md was published earlier as mcorbett51090/ravenclaude/technical-discovery.
Skill: technical-discovery
Invoked by:sales-engineer(primary);poc-evaluation-leadre-runs it lightly to confirm the pain a POC must prove.When to invoke: "I have a discovery call coming up"; "we're about to demo but haven't really discovered"; "what should I be uncovering?"; any deal where the pain isn't yet named and quantified.Output: a MEDDPICC-framed discovery plan + the pain/metric/decision-criteria questions to ask, captured in `../../templates/technical-discovery-notes.md`.
Procedure
- Frame the deal with MEDDPICC. Walk `../../knowledge/discovery-and-demo-playbook.md`: Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition. Mark which letters you already know and which are gaps — the gaps are your discovery agenda.
- Find the pain, then quantify it. A pain with no business impact ("it's a bit slow") doesn't sell. Push to the Metric: what does the pain cost in time / money / risk / missed revenue, and who feels it? This is the number the demo and the business case hang on.
- Map the decision. Who decides, against what criteria, by when, through what paper/procurement/security process? A technical win with no decision map stalls in procurement.
- Test for a champion, not just a contact. A champion has power, has personal pain, and will sell for you internally. Distinguish champion vs coach vs blocker.
- Capture and confirm. Write it into the discovery-notes template and reflect it back to the prospect ("so the critical issue is X, costing Y — did I get that right?"). Confirmed pain is the contract the demo is built against.
Output
The filled discovery-notes template + the prioritized list of remaining MEDDPICC gaps + a one-line critical business issue statement the demo will be built to resolve. Hand off to demo-design only once pain is named and quantified.
Anti-patterns this skill prevents
- Demoing into a vacuum (no discovered pain → a feature tour).
- A "pain" with no quantified business impact (nothing for the business case to stand on).
- Mistaking a friendly contact for a champion.
- Skipping the decision/paper process and getting ambushed by procurement or security late.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/sales-engineering/skills/technical-discovery/SKILL.md
Popularity
- Repository stars
- 8
- Repository forks
- 1
- 7-day trend score
- 16
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/mcorbett51090/ravenclaude/technical-discovery)