Extract structured insights from customer conversations into debriefs.
npx skills add https://github.com/CodeAlive-AI/ceo-ai-os --skill discovery-debrief
Please help me install this Agent Skill. Skill: discovery-debrief Source: https://github.com/CodeAlive-AI/ceo-ai-os/tree/main/skills/discovery-debrief Command: npx skills add https://github.com/CodeAlive-AI/ceo-ai-os --skill discovery-debrief
Discovery debrief turns a raw customer conversation into a structured decision aid so founders do not lose signal after the call. It helps distinguish real demand from polite interest, identify the current workaround, and capture the smallest sellable wedge.
Tell me about the customer conversation you just had, and I will turn it into a structured debrief with the key signals, hypothesis impact, and next step.
High-intent search queries and answers about installing and using this skill.
To extract structured insights from customer discovery interviews, you provide the raw conversation details for a sequential debrief. The process captures buyer versus user status, validates demand, identifies the status quo workaround, and logs actionable next steps.
Validating demand and separating real buying signals from polite interest requires evidence-tier assessment of the conversation. The debrief checks for payment intent, usage urgency, and workflow dependence to assign a demand tier and flag actionable decisions.
Tracking and comparing hypotheses against customer interview findings involves comparing call details with active memory files. The debrief flags whether the conversation confirms or refutes specific hypotheses and highlights which product decisions are ready now.
Yes, you can use this for founder sales follow-ups and prospect calls to find a sellable wedge. The debrief captures the smallest sellable wedge fit, detects repeated pain and trigger patterns, and records the conversation for ongoing memory.
Before logging a post-call debrief for product signals, you need the raw conversation details and any active hypothesis files for comparison. The debrief requires sequential one-question-at-a-time elicitation to accurately capture the dialogue and assess evidence tiers.
rchandnaWUSTLReformat unstructured customer conversation notes into a standardized field notes format.
semicolon-devteamCompile meeting, Slack, and PR decisions into a GitHub Discussion.
ajsai47Validate product ideas with structured YC-style office hours diagnostics.
valtterimelkkoAnalyze qualitative datasets through six-phase thematic analysis workflows.
