requirements-elicitation

Gap identification systematically analyzes product documents to pinpoint ambiguities and underspecified areas across technical dimensions like data, security, and performance. This reveals what stakeholders haven't detailed, preventing costly assumptions during implementation.

Targeted question generation creates specific, actionable questions grounded in source documents, explaining the technical impact of each ambiguity. This ensures stakeholders understand what information engineers need before development starts.

Risk assessment identifies and categorizes implementation, performance, security, and operational risks introduced by unclear requirements. A phase-based elicitation workflow produces concrete risk assessments tied directly to gaps in the product document.

Requirements elicitation works across PRDs, feature specifications, user stories, roadmaps, and one-pagers. The same gap-identification and question-generation workflow applies regardless of document format or level of detail.

After generating gap analyses and risk assessments, use stakeholder-specific questions to clarify requirements with Product Managers and Engineers. This feedback loop refines the specification before technical design and implementation begin.