Agent skill · Design & Presentation

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.

deanpetersgithub.com/deanpetersGitHub ↗
claude-codeNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill product-sense-interview-answer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/product-sense-interview-answer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,255
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## 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 Actuall

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. What Product Sense Interviews Actually Test
  5. The Six-Part Answer Spine
  6. Why This Works
  7. Anti-Patterns (What This Is NOT)
  8. When to Use This
  9. When NOT to Use This
  10. Application
  11. Delivery Rules
  12. Step 1: Clarify the Prompt
  13. Step 2: Build the Rationale Before the Feature
  14. Step 3: Define the Product Goal
Ships with 2 files
  • examples/improve-youtube.md
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the product-sense-interview-answer skill do?

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.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill product-sense-interview-answer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going