requirement-elicitation

Guide adaptive conversational elicitation of functional, nonfunctional, and edge-case project requirements.

1|Updated Aug 8, 2025

Search Tags:#planning #requirements #product management #discovery #elicitation #wizard

Ready to run

npx skills add https://github.com/britt/llpm --skill requirement-elicitation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirement-elicitation
Source: https://github.com/britt/llpm/tree/main/skills/requirement-elicitation
Command: npx skills add https://github.com/britt/llpm --skill requirement-elicitation

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the complex process of gathering detailed project requirements by guiding users through a structured, yet adaptive, conversational flow.

Core Features & Use Cases

Guided Requirement Gathering: Walks users through functional, nonfunctional, and edge-case requirements.
Domain Adaptability: Asks relevant questions based on project type (web app, API, CLI, etc.).
Use Case: A product manager can use this Skill to systematically define all necessary features, constraints, and user stories for a new mobile application, ensuring no critical aspect is overlooked.

Quick Start

Use the requirement-elicitation skill to start defining requirements for a new web application.

Frequently Asked Questions about requirement-elicitation

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

FAQPage Schema

How do I gather project requirements conversationally for a new web application?▼

To gather project requirements conversationally, use a guided wizard flow that prompts you for functional, nonfunctional, and edge-case needs. This structured elicitation process adapts its questions based on your specific project type, such as a web app or API.

What is the best way to define edge-case and nonfunctional requirements during product discovery?▼

Defining edge-case and nonfunctional requirements during product discovery involves a systematic elicitation process that queries constraints and boundary conditions. A structured wizard guides you through these specific scenarios to ensure no critical aspect is overlooked.

Can I use a conversational wizard to elicit requirements for data pipelines and APIs?▼

Yes, you can use a conversational wizard to elicit requirements for data pipelines and APIs. The domain-adaptable flow adjusts its questions based on the specified project type, ensuring relevant functional and nonfunctional needs are captured for various technical architectures.

How do I systematically document functional requirements and user stories for product management?▼

To systematically document functional requirements and user stories for product management, follow an adaptive conversational flow. This method ensures all necessary features and constraints are defined step-by-step, leveraging tools to save and retrieve the gathered information.

Does requirement elicitation work for different project types like mobile apps and CLIs?▼

Requirement elicitation works across different project types like mobile apps and CLIs by adapting its structured questioning flow. The wizard assesses the project domain and modifies its prompts to extract the most relevant functional and nonfunctional needs for that specific architecture.