What problem does it solve? Teams often jump into building software without a shared understanding of the problem, leading to misaligned features, unclear scope, and wasted engineering effort. This Skill structures the discovery of stakeholder needs so engineering starts from a clear, documented problem definition. ## Core Features & Use Cases - Structured Discovery Workflow: A seven-step procedure covering problem understanding, stakeholder identification, outcome discovery, functional and non-functional requirements, constraints, assumptions, and validation. - Template-Driven Outputs: Produces a Requirements Input document using the Requirements-Discovery template, with supporting Stakeholder Register and Project Definition templates. - SDLC Integration: Hands off elicited requirements to downstream skills like requirements analysis, user story definition, and acceptance criteria definition. - Use Case: When a stakeholder submits a vague feature request, use this Skill to clarify the problem, identify affected users, capture functional and non-functional expectations, and produce a structured requirements document ready for analysis. ## Quick Start Ask the AI to run requirements elicitation on your feature idea or problem statement to produce a structured requirements discovery document.
