Install every skill from this repository$ npx skills add asmartbear/asb-skills
Repository directory
Skills
7 of 7
#Skill8W activityInstalls
1asb-interview-debriefFacilitates the learning step of a proven customer-interview method — the recording half: turning raw material from ONE customer conversation (transcript, notes, memory dump) into a brief per-person debrief file, mapped against the numbered interview-question list (Q1, Q2, … with H-number tags). One concise answer per question actually asked, key phrases kept verbatim, unasked questions honestly skipped, a one-line commentary only where in-the-moment context helps later analysis, and an addenda section for everything heard that fit no question. Load when the user has just done a customer interview and says 'here's the transcript,' 'process my call notes,' 'file this conversation against my questions,' or 'add this interview to the record.' Do NOT load for writing goals, hypotheses, or interview questions (earlier steps), for synthesizing patterns across multiple interviews and updating hypotheses (the next step), or for summarizing meetings or transcripts unrelated to customer interviews.62asb-interview-hypothesesFacilitates the second step of a proven customer-interview method: recording the user's current best guesses — hypotheses — as numbered, falsifiable statements (H1, H2, …), each mapped to the goal questions it addresses, so interviews can confirm or contradict them instead of confirmation bias quietly filtering what's heard. Takes a GOALS.md goal-question list as input (file or pasted), elicits what the user believes goal by goal, sharpens vague beliefs into testable claims, prunes to hypotheses whose resolution would actually change what the user builds, targets, charges, or says, and preserves the result in HYPOTHESES.md. Load when the user has goal questions and wants to write hypotheses, list their assumptions, or record predictions before interviewing customers — 'I have my goals, what's next,' 'help me write down what I believe about my customers.' Do NOT load for writing the interview questions themselves, for analyzing interviews already conducted, or for statistical hypothesis testing.63asb-interview-learningFacilitates the learning step of a proven customer-interview method — the synthesis half: reads a directory of per-interview debrief files against the working HYPOTHESES.md and QUESTIONS.md and proposes evidence-cited updates ONE at a time — double down, tune numbers, mark disproved, park heard-once observations in a 'That's funny' watch section, add new hypotheses with new questions — applying each agreed change directly to the files with a change log, and ending with a stop-or-continue-or-re-aim verdict on the interviewing itself. Load when the user says 'what did we learn from these interviews,' 'update my hypotheses from the interviews,' 'synthesize my interview notes,' or 'should I keep interviewing?' Do NOT load for recording a single conversation into a debrief (the previous step), for writing initial goals, hypotheses, or interview questions (earlier steps), or for deciding what to build next (comes after this method).64asb-interview-questionsFacilitates the third step of a proven customer-interview method: translating hypotheses into open-ended, unbiased interview questions — each a miniature experiment designed to test one hypothesis without leading the witness. Two modes: given a single hypothesis, it grills the question into shape and outputs the final question in chat; given a HYPOTHESES.md file, it iterates the whole list, grouping related hypotheses, and maintains a QUESTIONS.md file (numbered Q1, Q2, … mapped to H-numbers) as a live, resumable artifact. Load when the user has hypotheses and wants interview questions, asks how to phrase a question for customers without biasing the answer, or says 'turn my hypotheses into questions' or 'help me ask about X without leading.' Do NOT load for writing goal questions or hypotheses (earlier steps), for conducting or analyzing the interviews themselves, for survey/questionnaire design, or for job interviews.65asb-interview-reportFacilitates the final step of a proven customer-interview method: distilling everything a round of interviews produced (GOALS.md, HYPOTHESES.md, QUESTIONS.md, and a directory of per-interview debriefs) into a single FINAL-REPORT.md the whole company can use. Top: a summary as brief as possible without losing salient information. Below: numbered findings (F1, F2, …) tagged validated / disproved / directional / watch / untested, every one citing debriefs and quoting customers verbatim, plus per-area briefs that marshal the evidence for ideal-customer definition, positioning, pricing, marketing & sales, and product priorities. Load when the user says 'write up what we found from the interviews,' 'summarize the interview results for the team,' or 'turn the interviews into a report.' Do NOT load for updating hypotheses from interviews (the synthesis step), for recording one conversation (the debrief step), or for actually doing the positioning, ideal-customer, or pricing work the report feeds.66asb-who-meInterrogates the user to discover who they actually are — what drives them, what drains them, and the natural strengths they can't see because they come so easily — using proven self-discovery prompts (even-as-a-kid, lost-in-the-work, pit-of-my-stomach dread), the anti-questions, and outside-in questions given as homework to people who know them (perfect scenario, personal hell, invisible strengths). Presses every self-flattering label into concrete episodes, welcomes socially unacceptable motives (money, fame, proving a point), and records each finding in WHO-ME.md as a non-judgmental fact — a strength in some contexts, a hindrance in others — with the contexts where it helps and hurts. Load when the user asks who they really are, what work fits them, what drives or drains them, why they keep burning out, or what to build given who they are. Do NOT load to inventory a company's or product's strengths or to distill the one or two decisive personal advantages — the voters step, which consumes this file.67asb-rude-qaInterrogates a user's decision, plan, pitch, positioning, target market, pricing, or still-forming idea with sharp, unsparing questions — extended when useful to hostile or even unfair framings — until the plan sharpens into defensible decisions, or the user concludes it isn't a good idea after all. Acts as the constructive devil's advocate that the user cannot be for themselves. Load when the user wants to stress-test, attack, pressure-test, find holes in, or play devil's advocate against something they're attached to; when they ask to be \"grilled,\" \"beat up,\" or told \"why I'm wrong\"; when they suspect their plan contains wishful thinking, fluffy language, or an unnamed elephant in the room; or when they need to convert vague aspirations into real strategic decisions (with consequences accepted). Do NOT load for ordinary code review, prose editing, or general feedback requests without an adversarial frame.5