product-sense
Skill25 starsChanged 9 months agoMITView on GitHub
Structured product sense/design framework for AI product roles. Covers: design a product, improve X, productize a capability.
In this repository16 other files it gives its agents.
- ai-ethics-tradeoffsSkill
- ai-market-landscapeSkill
- ai-product-teardownSkill
- analytical-pmSkill
- behavioral-pmSkill
- launch-checklistSkill
- metric-dashboardSkill
- mock-interviewerSkill
- pm-case-studySkill
- pm-writingSkill
- prd-writerSkill
- prioritization-matrixSkill
- product-strategySkill
- stakeholder-briefSkill
- technical-pmSkill
- user-research-synthesisSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Ask 3-5 clarifying questions before proceeding.
- Distinctive: line 35
After listing questions, state reasonable assumptions for each and proceed.
- Distinctive: line 92
When the question is about an AI company product, layer in:
- Distinctive: line 103
Before generating the answer:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Sense Skill
Apply a structured framework to PM product sense / product design questions targeting AI product roles.
When to Use
- User asks a "Design a product for X" question
- User asks "How would you improve X"
- User asks "How would you productize X capability"
- User says
/product-sensefollowed by a question - Any product design, product sense, or "build a product" interview question
Context
- Tuned for: AI product roles at frontier AI companies
- What matters: First-principles thinking, ambition, structured clarity, and taste
- Common pitfall: Rushing to solutions without clarifying the problem first. Always start with clarifying questions.
Framework: Product Sense (6 Sections)
Generate the answer following this EXACT structure. Each section should be substantive - not just headers.
Section 1: Clarifications (ASK FIRST, ALWAYS)
Ask 3-5 clarifying questions before proceeding. Categories:
- Scope: What company are we? What's the form factor? Platform constraints?
- Users: Who is the primary audience? B2C vs B2B vs B2B2C?
- Business: What stage is the company? Revenue model? Strategic priorities?
- Technical: What capabilities exist? What's feasible in the timeframe?
- Constraints: Budget, timeline, regulatory, geographic?
After listing questions, state reasonable assumptions for each and proceed.
Section 2: Product Strategy & Rationale (WHY BUILD THIS)
- Company Mission: How does this align with the company's stated mission? Reference the specific company's mission statement and connect your product thinking to it.
- Trends & Tailwinds: What macro trends make this timely? (AI adoption curves, regulatory shifts, user behavior changes)
- Competition: Who else is doing this? What's the gap?
- Strategic Moat: What unique advantage does this company have here?
- Product Goal: One sentence on what we're building and why NOW
Section 3: User Segmentation (WHO)
Segment users along 3 dimensions and pick a primary:
- Reach: How many potential users in each segment?
- Frequency: How often would they use this?
- Underserved: How poorly served are they today?
For each segment provide: persona name, description, why they'd use this, current alternatives.
Pick primary segment with clear rationale (usually: highest frequency + most underserved).
Section 4: User Journey & Pain Points (WHAT HURTS)
Map the user journey for the primary segment:
- Discovery/Awareness
- Onboarding/First Use
- Core Usage Loop
- Retention/Return
For each stage, identify pain points scored on:
- Severity (1-3): How painful is this?
- Frequency (1-3): How often does it occur?
- Alternatives (1-3): How well do current solutions address this?
Pick top 2-3 pain points to solve. Justify the prioritization.
Section 5: Solutions (HOW)
For each selected pain point:
Brainstorm (3-4 options per pain point, range from incremental to ambitious)
Evaluate each on:
- Impact on pain point (High/Med/Low)
- Engineering effort (High/Med/Low)
- Strategic alignment (High/Med/Low)
- Differentiation (High/Med/Low)
Recommend top solution with clear rationale. Describe:
- What the user sees/experiences (be concrete and specific)
- Key features for V1 vs V2
- Why this is better than alternatives
Section 6: Success Metrics
- North Star Metric: One metric that captures the core value delivered
- Supporting Metrics (3-4): Leading indicators that the NSM will grow
- Counter/Guardrail Metrics (2-3): What we must NOT break (safety, quality, trust)
- How to measure: What instrumentation is needed?
AI Company Flavor
When the question is about an AI company product, layer in:
- Safety considerations: How does this product avoid harm? What guardrails exist?
- Model capabilities: What model capabilities enable this? What's the technical frontier?
- Scaling dynamics: How does this get better with more users/data?
- Mission alignment: Tie back to the specific company's mission
- Taste: Match the company's culture — some labs value ambitious, creative, step-change thinking; others value careful, principled, safety-first thinking; others value scientific rigor. Research the specific company's values beforehand.
Output Format
Structure the response as a conversational walkthrough — structured but natural. Use the section headers. Aim for ~2500 words total. Flag where you'd pause for discussion or input.
Research-First Workflow
Before generating the answer:
- Research — Use web search to find latest thinking from AI company blogs, PM thought leaders, market data, competitor intel. Do 5-10 searches.
- Cite sources — Include
[linked source](url)inline for major claims, data points, and trends. - Display the complete structured answer.
What Good Looks Like
- Starts with clarifying questions (CRITICAL)
- Shows strategic thinking before jumping to solutions
- User empathy is specific and grounded (not generic)
- Solutions are creative AND feasible
- Metrics are specific and tied to user value
- Mentions trade-offs and what you'd NOT build
- Ties back to company mission
- Shows taste and opinion (not just framework execution)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

