product-discovery
Product Discovery Skill
Transform vague ideas into actionable specifications through structured questioning.
Core Methodology
Questioning Frameworks
Five Whys - Reach root problems:
- "Why is this a problem?" → Surface answer
- "Why does that matter?" → Deeper impact
- Continue until you reach the core motivation
MECE (Mutually Exclusive, Collectively Exhaustive):
- Cover all aspects without overlap
- Users, features, constraints, success criteria
Socratic Probing:
- Never accept surface-level answers
More from benshapyro/cadre-devkit-claude
frontend-design
Create distinctive, memorable user interfaces that avoid generic AI aesthetics. Use when designing UI/UX, planning visual direction, or building pages and layouts.
10error-handler
Provides battle-tested error handling patterns for TypeScript and Python. Use when implementing error handling, creating try/catch blocks, or handling exceptions.
5react-patterns
Modern React patterns for TypeScript applications including hooks, state management, and component composition. Use when building React components, managing state, or implementing React best practices.
4tailwind-conventions
Consistent Tailwind CSS patterns for React/Next.js applications. Use when styling components with Tailwind, adding responsive design, implementing dark mode, or organizing utility classes.
4test-generator
Generates Jest or Pytest tests following Ben's testing standards. Use when creating tests, adding test coverage, writing unit tests, mocking dependencies, or when user mentions testing, test cases, Jest, Pytest, fixtures, assertions, or coverage.
3devkit-knowledge
Knowledge base for the Cadre DevKit. Use when answering questions about the devkit structure, commands, skills, hooks, agents, or workflows.
3