Agent skill · product strategy · deanpeters
product-sense-interview-answer
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
Why this skill is useful
Provides a structured framework for articulating product-sense answers that helps candidates prioritize and clarify their thoughts effectively.
What it needs
About 7k tokens when loaded. Last updated 2026-07-17. 6,302 stars on the source repository.
What this skill does
Purpose Help PM candidates and interview coaches structure product-sense answers that sound strong out loud, not just on paper. Use this when practicing prompts like "How would you improve X?", "Design a product for Y", or "What would you build next for Z?" This is not a memorize-and-recite script. It is a reasoning scaffold that prevents solution-jumping, forces real prioritization, and leaves the interviewer with a clean story they can follow. Input Works best with: The interview prompt you're practicing (e.g., 'How would you improve X?', 'Design a product for Y'). Also useful: The company/role you're interviewing for and how much time the answer gets. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. Arriving empty-handed? That works too. The skill asks for the prompt, then walks the reasoning scaffold with you out loud. Example invocation: Practice this: 'How would you improve Google Maps for commuters?' — 25-minute answer, L5 PM loop. Key Concepts What Product Sense Interviews Actually Test Strong product-sense answers do more than generate ideas. Interviewers are usually testing whether you can: Clarify ambiguous prompts without getting stuck Tie user value to market or business logic Segment thoughtfully instead of talking about "everyone" Prioritize one pain point instead of describing ten equally Make tradeoffs explicit when choosing an MVP Communicate clearly under time pressure The Six-Part Answer Spine 1. Clarify - Reduce ambiguity, define scope, and state assumptions. 2. Rationale - Explain why the problem matters now for the market and, if relevant, the company. 3. Product Goal - Define the user outcome you want to create before talking about features. 4. Segmentation - Choose who to serve first and show why that target wins. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills deanpeters/product-sense-interview-answer