Interactive discovery interview → structured product spec. Triggers: spec, PRD, requirements, scoping, brainstorming, new project. Uses AskUserQuestion; WebSearch/WebFetch when user wants research. Outputs user stories, acceptance criteria, constraints.
99
100%
Does it follow best practices?
Impact
96%
2.28xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
A startup founder named Alex has reached out wanting to build a fitness tracking app. Alex is a non-technical entrepreneur who has been doing some research but has many uncertainties about the right approach. You need to conduct a structured discovery interview with Alex to gather all the requirements needed to produce a solid product specification.
Alex's profile: First-time app founder, non-technical, has a rough idea but hasn't thought through all the details. Alex often says "I'm not sure" and is open to being educated. Alex will answer questions but frequently defers technical decisions and is unsure about scale, storage, and technology choices.
To complete this task, play both roles: conduct the interview as the interviewer and provide Alex's responses as a realistic non-technical founder who hasn't fully thought through all details. Conduct the full discovery interview process and document everything.
Produce the following files:
interview_log.md — A full transcript of the discovery interview showing each question asked (including the full question text and all answer options presented) and the simulated answer chosen. Label each exchange clearly (Q1, Q2, etc.). Include all phases of the interview process.
docs/specs/ — The final specification file using whatever naming convention you choose. The spec must be complete and reflect everything learned in the interview.
The interview log is critical — it must capture the complete interview including all options presented for every question.