requirements-elicitation

Installation
SKILL.md

Requirements Elicitation Skill

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.

Core Philosophy

ELICIT, DON'T INVENT

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.

Key Principles

  1. Identify ambiguity - Point out where requirements are unclear or underspecified
  2. Ask targeted questions - Generate specific, actionable questions organized by stakeholder
  3. Assess risk - Evaluate technical risks introduced by missing requirements
  4. Avoid assumptions - Never invent technical details (tech stack, architecture, data models) that aren't specified
  5. Stay grounded - Always reference the source document; don't add scope or features

When to Use This Skill

Related skills

More from exploration-labs/nates-substack-skills

Installs
11
GitHub Stars
30
First Seen
Feb 9, 2026