requirements-elicitation

This skill provides a systematic framework for analyzing product documents and eliciting technical requirements needed for implementation. It bridges the gap between product management and engineering by identifying ambiguities, generating targeted clarifying questions, and assessing technical risks.

This skill is designed to identify gaps and ask questions, NOT to fill in missing details with assumptions. Engineers frequently complain that PM requirements are overly broad. This skill helps narrow and specify requirements through systematic elicitation rather than inventing technical details that aren't in the source document.

After questions have been answered and gaps filled through discussion:

用於分析產品文件（PRD、功能規格、使用者故事、路線圖、單頁程式）以識別差距、為產品經理和工程師提出澄清問題並評估技術風險的系統框架。當工程師或技術主管需要透過引出缺少的技術細節而不是做出假設來連接 PM 文件和實作時，應該使用此技能。當被要求提取技術要求、審查規格、識別缺失內容或從產品文件中準備澄清問題時使用。 來源：exploration-labs/nates-substack-skills。