feature-interview
Feature Interview Skill
You are a senior product engineer conducting a thorough discovery session for a new feature. Your job is to ask probing, insightful questions that the user might not have considered—questions that reveal hidden complexity, edge cases, and design decisions that will affect implementation.
Process
Phase 1: Initial Understanding
Read any context the user provides about the feature. Before asking questions, briefly acknowledge what you understand so far.
Phase 2: Deep Interview
Use AskUserQuestion repeatedly to explore the feature from multiple angles. Do not ask obvious questions. Instead, ask questions that:
- Reveal hidden assumptions
- Expose edge cases the user hasn't considered
- Uncover tradeoffs they'll need to make
- Challenge the proposed approach constructively
- Identify dependencies and constraints
More from neonwatty/claude-skills
think-through
A Socratic interview skill for thinking through technical ideas like apps, products, tools, and projects. Use this when the user says "think through [idea]", "help me think about [app/product]", "let's explore [project idea]", or wants to iterate on a technical concept before building. Asks probing questions about the problem, target users, market, technical approach, tradeoffs, and viability. Continues until the idea is well-explored, then produces a written summary and proposes directions.
22mobile-ux-ci
Generates Playwright tests that detect iOS/mobile UX anti-patterns in CI. Use this when the user says "mobile ux ci", "detect anti-patterns", "ios ux checks", "automated ux testing", "prevent ux regressions", or "add mobile ux checks". Creates tests that FAIL when anti-patterns are found (hamburger menus, FABs, small touch targets, Material Design components), enforcing iOS Human Interface Guidelines in CI.
18browser-workflow-generator
Generates, creates, or updates browser workflow files. Use this when the user says "generate browser workflows", "create browser workflows", "update browser workflows", "iterate on browser workflows", or "discover browser workflows". Explores the app's codebase to discover all user-facing features, routes, and interactions, then creates comprehensive numbered workflows with substeps covering the full user experience.
18ios-workflow-executor
Executes web app workflows in Safari on the iOS Simulator from /workflows/ios-workflows.md. Use this when the user says "run ios workflows", "execute ios workflows", "test ios workflows", or "test on ios simulator". Tests each workflow step by step in mobile Safari using iOS Simulator MCP, captures before/after screenshots, audits for iOS HIG anti-patterns, documents issues, and generates HTML reports with visual evidence.
17pr-creator
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", or "pr for these changes". Does NOT merge - stops when CI passes and provides the PR link.
15browser-workflow-executor
Executes browser-based user workflows from /workflows/browser-workflows.md using Claude-in-Chrome MCP. Use this when the user says "run browser workflows", "execute browser workflows", "test browser workflows", or "audit browser flows". Tests each workflow step by step, captures before/after screenshots, documents issues, and generates HTML reports with visual evidence of fixes.
15