Loading...
Loading...
Found 21 Skills
Continuously interview users around a plan or design until a shared understanding is reached, and address each branch of the decision tree one by one. Use this when the user wants to stress-test a plan, have their design grilled, or mentions "grill me".
Summarize a user interview transcript into structured insights with key themes, quotes, and action items. Use after conducting user interviews to extract and share findings efficiently.
Master user research with interviews, surveys, personas, journey mapping, and research synthesis for user-centered design.
Interviews the user about a product idea or feature using structured questions, then generates a detailed spec document (SPEC.md). Use when the user wants to flesh out an idea, plan a feature, or create a buildable specification.
Interview user to clarify any topic - exploring codebase, investigating issues, planning features, understanding requirements, or drilling into plans. Socratic questioning to uncover details.
Conduct an interactive discovery interview to produce a structured product specification. Triggers: write a spec, PRD, feature spec, requirements, product requirements, scope a project, brainstorm a feature, flesh out an idea, plan a new project. Uses AskUserQuestion for all user choices; WebSearch/WebFetch when the user wants research. Outputs: user stories, acceptance criteria, technical constraints, prioritized requirements in docs/specs/ per SPEC_TEMPLATE.md. Do NOT use for: implementation, code review, debugging, refactors, or when the user already has a complete spec they only want edited.
Deep user interview for pivotal plan/design uncertainties. Auto-suggest when user judgment would materially change scope, approach, or success criteria. Scoped mid-task grilling for subtask-pivotal forks. NOT for micro-reversible questions or codebase-discoverable facts.
Run developer customer discovery via a Technical Advisory Board (TAB). Use when the founder has never interviewed a user who isn't a friend, is inventing messaging from a conference room, or is guessing at the roadmap instead of hearing the pain firsthand.
Proactive requirements gathering - systematically interviews the user to uncover ambiguities, preferences, and constraints BEFORE implementation begins.