Discovery Call Assistant

Captures structured notes, follow-up questions, and pain points during live discovery calls.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sparkst/sparkry-claude-skills --skill discovery-call-assistant-sparkst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Discovery Call Assistant
Source: https://github.com/sparkst/sparkry-claude-skills/tree/main/plugins/interview-toolkit/skills/discovery-call
Command: npx skills add https://github.com/sparkst/sparkry-claude-skills --skill discovery-call-assistant-sparkst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Consultants and service providers often leave discovery calls with scattered notes, missed follow-up questions, and unquantified client pain points, making it hard to build accurate proposals afterward. ## Core Features & Use Cases - Structured Note-Taking: Captures conversation in a sectioned Markdown template covering business context, pain points, tools, solution reactions, and day-in-the-life workflows. - Follow-Up Question Suggestions: Proposes probing questions for pain points, tech stack satisfaction, business impact, and solution validation when answers are vague. - Pain Point Extraction: Categorizes pain points by type (time_sink, quality, gap, frustration) and severity based on trigger phrases and frequency. - Time Management: Tracks per-section timing against a 45-minute call budget and issues non-intrusive alerts. - Use Case: A freelance consultant runs a 45-minute discovery call with a potential client, uses the assistant to capture verbatim quotes and ranked pain points, then hands the synthesis-ready notes to a proposal-writing workflow. ## Quick Start Start a discovery call session for client Acme Corp and help me take structured notes, suggest follow-up questions, and track time across all interview sections.

Frequently Asked Questions about Discovery Call Assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I take structured notes during a client discovery call?▼

Use a sectioned note template aligned with the call agenda: business context, pain points, current tools, solution reactions, and day-in-the-life. The assistant captures responses per section in Markdown and flags gaps before the call ends.

How to identify and categorize client pain points in interviews?▼

Listen for trigger phrases like "takes forever" or "drowning in" and classify each pain point by category (time_sink, quality, gap, frustration) and severity based on frequency and language intensity. Each pain point is recorded with the client's verbatim wording.

What follow-up questions should I ask in a discovery call?▼

Probe pain point frequency and cost ("How much time does that cost per week?"), tool satisfaction on a 1-5 scale, and solution validation ("Would this actually save time?"). The assistant suggests context-appropriate questions when answers are vague.

Can this assistant work for calls longer or shorter than 45 minutes?▼

The default timing budget targets 45 minutes with per-section targets and alert thresholds, but the section structure is flexible. The Pain Points section intentionally allows overtime since it carries the most value.

What happens to the notes after the discovery call ends?▼

Notes are finalized into a synthesis-ready Markdown file with a ranked pain points summary, tech stack table, solution matches, quotes, and red flags. This output feeds directly into a downstream interview-synthesis skill for proposals.