Index/ Claude Skills/ Transcript Analysis: Discovery Pipeline
Claude skill · transcripts to discovery reports

Transcript Analysis — Discovery Pipeline

Four steps from raw input to actionable recommendations: extract, analyze, map, report. Every finding is traceable to an explicit or implicit client signal with a confidence level.

01

The pipeline

InputMeeting transcript
Email chains, chat logs, audio transcription, process descriptions.
STEP 1Data
extraction
Statements, sentiment markers, metrics, gaps, direct quotes.
STEP 2Deep
analysis
Dual-lens signal detection — what’s said and what’s meant.
EXPLICIT Direct pain points, feature requests, clear objections, measurable metrics.
IMPLICIT Hesitations, conspicuous absences, tone shifts, assumptions, comparative language.
Advanced techniques — chain of thought, chain of density, few-shot learning — feed this step.
STEP 3Map insights
to solutions
For every finding, four moves:
SIGNAL Identify the signal — quote or observation, tagged explicit / implicit.
NEED Interpret the need — underlying pain point, why it matters.
IMPACT Categorize — short-term friction, long-term strategic, UX issue, business outcome.
ACTION Recommend — quick wins (days/weeks) vs. strategic (months/quarters), each with confidence.
STEP 4Produce
report
Seven structured sections — executive summary, explicit pain points, implicit insights, quick wins, strategic recommendations, open questions, next steps.
Quality gate
PassReport delivered
Clean output to the client.
Flagged — error pathsHandle
the edge
AMBIGUOUS Flag it + request clarification.
CONTRADICTORY Surface both, let stakeholders decide.
MISSING Note gaps, suggest how to fill.
LOW CONFIDENCE Mark clearly, separate from high.
02

Pipeline steps

STEP 1Data
extraction
Thorough review of all transcript text and supporting materials.
  • Extract direct statements, sentiment markers, and metrics
  • Capture gaps, hesitations, or omissions that signal underlying issues
  • Pull direct quotes that anchor each finding
STEP 2Deep
analysis
Dual-lens signal detection.
  • Explicit: pain points, feature requests, objections, metrics
  • Implicit: hesitations, absences, tone shifts, assumptions, comparative language
  • Chain of Thought, Chain of Density, and Few-Shot techniques available for complex cases
STEP 3Map insights
to solutions
Four-part mapping for every finding.
  • Identify the Signal — quote or observation, tagged explicit/implicit
  • Interpret the Need — underlying pain point, why it matters
  • Categorize Impact — short-term friction, strategic, UX, or business outcome
  • Recommend — quick wins vs. strategic, each with a confidence level
STEP 4Produce
report
Structured output with seven sections.
  • Executive Summary — 2–3 sentence overview
  • Explicit Pain Points — quote + impact + recommendation
  • Implicit Insights — signal + interpretation + action
  • Quick Wins, Strategic Recommendations, Open Questions, Next Steps
03

Signal detection

The core differentiator: two parallel signal detectors that catch what’s stated and what’s left unsaid.

Explicit
signals
• Direct statements of pain points
• Specific feature requests
• Clear objections or concerns
• Measurable metrics mentioned
Implicit
signals
• Hesitations, pauses, or deflections
• What’s conspicuously NOT mentioned
• Tone shifts or emotional markers
• Underlying assumptions revealed by phrasing
• Comparative language (“unlike X…”)
• Future-focused concerns signaling strategic anxiety
04

Output structureseven-section report

Every recommendation is traceable to a signal, tagged with a confidence level, and paired with a timeline.

1 · Executive Summary
2–3 sentence overview of key findings — the “so what?”
2 · Explicit Pain Points
Direct quotes → impact assessed → recommendation with confidence level.
3 · Implicit Insights
Observed signal → interpretation → recommendation with confidence level.
4 · Quick Wins
Actions achievable in days/weeks — prioritized, with timelines.
5 · Strategic Recommendations
Multi-month initiatives — phased, with milestones.
6 · Open Questions
What needs clarification — gaps documented, assumptions stated.
7 · Next Steps
Prioritized action list.
05

Quality standards & error handling

Every output is gated. Ambiguous, contradictory, or low-confidence findings are flagged rather than silently included.

Quality
standards
TRACEABLE Every recommendation anchored to a client signal.
CONFIDENCE High / Medium / Low on every finding.
AMBIGUITY Contradictory data surfaced to stakeholders.
GAPS Missing information noted, with a plan to obtain it.
Error
handling
AMBIGUOUS Flag it, request clarification, document assumptions.
CONTRADICTORY Surface both interpretations, let stakeholders decide.
MISSING Note gaps explicitly, suggest how to fill them.
LOW CONF. Mark clearly, separate from high-confidence findings.
Communication styleEvidence-based (every claim backed by data or clear inference) · action-oriented (so what? and what next?) · transparent (show your work) · structured (bullets, headings, consistent formatting) · professional but accessible (rigor without jargon overload).