bee:interviewing-user

You clarify requirements before coding by systematically interviewing users to uncover ambiguities, preferences, and constraints. This structured questioning process identifies unclear architectural decisions and behavioral requirements, presenting a validated understanding summary for user confirmation.

Structured questioning for requirements gathering is a systematic interview process that analyzes task descriptions to pinpoint areas needing clarification. It guides users through targeted questions about architecture choices, edge case behaviors, and performance constraints to ensure implementation aligns with user needs.

You identify ambiguities in task descriptions by proactively analyzing them to uncover hidden constraints and unclear aspects. The skill detects unclear architectural decisions and limitations, then asks targeted questions to resolve them before any implementation begins.

Yes, you can use a user interview skill to resolve edge case behaviors and performance constraints. It systematically guides you through a question-and-answer process to uncover these specific behavioral requirements and limitations before you start coding.

The best way to validate understanding of architectural decisions is through a structured question-and-answer process that ensures clarity. The skill presents a validated understanding summary for explicit user confirmation before any development effort begins.

You need to perform ambiguity resolution for a new software module before any implementation begins. Proactively resolving unclear behavioral requirements and limitations at this stage prevents wasted development effort and ensures the final implementation aligns with user needs.