asb-interview-report

Distills customer interview debriefs and hypotheses into a cited final findings report.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-interview-report-evanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asb-interview-report
Source: https://github.com/evanish/reusable-PM-templates/tree/main/Templates%20to%20reuse/Work/asb-customer-discovery/asb-interview-report
Command: npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-interview-report-evanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a round of customer interviews, the learning scatters across hypothesis files, question lists, and per-interview debriefs that nobody rereads. This Skill consolidates all of it into a single FINAL-REPORT.md that states what is now known, what is merely believed, and what remains untested, with every claim backed by tallies, debrief citations, and verbatim customer quotes. ## Core Features & Use Cases - Evidence-graded findings: Every finding is numbered (F1, F2, ...) and tagged validated, disproved, directional, watch, or untested, with exact voice tallies like "7 of 9" instead of vague probability words. - Two-layer report structure: A citation-free summary for skimmers on top, and a fully cited body with quotes and debrief references below for deep readers and downstream LLM work. - Per-area briefs: Marshals findings for ideal-customer definition, positioning and messaging, pricing and packaging, marketing and sales, and product priorities, without doing that downstream work itself. - Use Case: After completing eight customer discovery interviews with debriefs on file, ask for a report and receive a FINAL-REPORT.md the whole company can use, including sampling-bias disclosure and a vocabulary bank of the customers' own words. ## Quick Start Write up what we found from the interviews in this directory into a final report for the team.

Frequently Asked Questions about asb-interview-report

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

FAQPage Schema
How do I turn customer interview notes into a summary report?

Provide the hypothesis file, question list, goals, and the directory of per-interview debriefs, then ask for the interview report. The Skill sweeps all sources, assigns numbered findings with evidence tallies and verbatim quotes, and writes a FINAL-REPORT.md with a brief summary on top and full citations below.

What inputs does the interview report skill need?

It needs the method's working files (GOALS.md, HYPOTHESES.md, QUESTIONS.md) and a directory of per-interview debriefs, which are the primary sources every finding cites. Raw transcripts must be converted into debrief records first; with zero debriefs there is nothing to report.

Can I use this report if the interviews were never synthesized?

Yes, but the report will perform first-pass synthesis itself and label the output as a snapshot, noting that HYPOTHESES.md does not reflect the findings. The Skill offers to run the synthesis step first if a synthesis skill is installed.

What are the limitations of an interview findings report?

With three or fewer debriefs the report cannot support validated findings and is delivered as a thin report of directional and watch items. It also refuses to inflate evidence strength, fabricate citations, or produce the downstream positioning, pricing, or roadmap work itself.

How are findings validated in a customer interview report?

Each finding carries a status mark: validated, disproved, directional, watch, or untested, matched strictly to the evidence. Tallies are exact counts with honest denominators, and statuses only change when evidence is re-examined or added, never by user preference.