requirements-elicitation

Name: requirements-elicitation
Availability: InStock
Author: kwoekel

Identify gaps in product documents and generate clarifying questions.

Updated Apr 11, 2026

Search Tags:#product management #clarifying questions #requirements elicitation #technical risk assessment #product documentation analysis

Ready to run

npx skills add https://github.com/kwoekel/Jones --skill requirements-elicitation-kwoekel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-elicitation
Source: https://github.com/kwoekel/Jones/tree/main/skills/requirements-elicitation
Command: npx skills add https://github.com/kwoekel/Jones --skill requirements-elicitation-kwoekel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps engineers and technical leads systematically analyze product documents to identify gaps, generate clarifying questions, and assess technical risks, ensuring that assumptions are minimized and communication is clear between product management and engineering.

Core Features & Use Cases

Systematic Analysis: Analyze PRDs, feature specs, user stories, roadmaps, and one-pagers for technical requirements.
Question Generation: Create targeted clarifying questions for PMs and engineers to fill in missing technical details.
Risk Assessment: Evaluate technical risks introduced by missing requirements.
Use Case: When reviewing a PRD for a new feature, use this Skill to identify gaps in the technical requirements and generate questions to discuss with the product team.

Quick Start

Analyze the attached PRD 'new_feature_prd.md' for technical requirements and generate clarifying questions.

Frequently Asked Questions about requirements-elicitation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify gaps in technical requirements from a PRD?▼

To identify gaps in technical requirements from a PRD, you need systematic requirements elicitation to analyze product documents and highlight missing technical details. This ensures assumptions are minimized by pinpointing exactly where specifications lack engineering clarity for follow-up.

How do I generate clarifying questions for product managers and engineers?▼

You generate clarifying questions for product managers and engineers by analyzing feature specs and user stories against technical risk frameworks. This systematic analysis produces targeted questions that fill in missing technical details and bridge communication gaps between teams.

What is the best way to assess technical risk from missing product documentation?▼

Assessing technical risk from missing product documentation involves evaluating incomplete requirements against established risk frameworks. This reveals vulnerabilities introduced by missing details, allowing teams to proactively address potential engineering issues before development begins.

Can I analyze one-pagers and user stories for technical completeness?▼

Yes, you can analyze one-pagers and user stories for technical completeness. Systematic requirements elicitation processes these product documents alongside PRDs and roadmaps to detect missing technical requirements and generate necessary clarifying questions.

Do I need technical knowledge of product development processes to use requirements elicitation?▼

Yes, requirements elicitation requires technical knowledge of product development processes and risk assessment. This domain expertise is necessary to effectively evaluate product documentation, understand technical dimensions, and formulate relevant clarifying questions.