user-elicit

Generates User Requirements Documents from structured stakeholder elicitation sessions.

2|Updated Feb 7, 2026

Search Tags:#workflow #requirements #elicitation #product-management #stakeholders #phase-2 #URD

Ready to run

npx skills add https://github.com/dayvidpham/aura-plugins --skill user-elicit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-elicit
Source: https://github.com/dayvidpham/aura-plugins/tree/main/skills/user-elicit
Command: npx skills add https://github.com/dayvidpham/aura-plugins --skill user-elicit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams systematically capture stakeholder requirements and convert them into a single source of truth URD.

Core Features & Use Cases

Structured URE survey to capture stakeholder requirements
URD creation as the single source of truth
Guidance for Phase 2 steps and dependencies to Phase 3

Quick Start

Launch the elicitation workflow to design Phase 2 questions, collect stakeholder responses, and generate the URD document.

Frequently Asked Questions about user-elicit

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

FAQPage Schema

What is user requirements elicitation in product management?▼

User requirements elicitation is the structured process of gathering stakeholder input to define product needs. This Skill facilitates the process by applying structured elicitation prompts to stakeholder responses, converting them into a single source of truth URD document.

How do I create a URD from stakeholder input?▼

To create a URD from stakeholder input, launch the structured elicitation workflow to design Phase 2 questions and collect responses. The Skill then processes these stakeholder requirements to generate the URD document as the single source of truth.

How do I plan cross-task dependencies for Phase 2 elicitation?▼

Plan cross-task dependencies for Phase 2 elicitation by referencing Phase 1 findings and defining Phase 3 handoff criteria. The Skill specifies dependency planning within the product workflow to ensure smooth transitions between elicitation and downstream phases.

Do I need Phase 1 findings before starting URD creation?▼

Yes, Phase 1 findings are required before starting URD creation. The Skill explicitly references Phase 1 findings as input for designing the structured elicitation prompts and establishing the baseline for Phase 2 stakeholder surveys.

What is the best way to structure requirements elicitation surveys?▼

The best way to structure requirements elicitation surveys is using a YAML frontmatter entry with structured elicitation prompts. This approach ensures systematic capture of stakeholder requirements for URD creation in product development workflows.

Can I use this workflow for cross-task dependency planning?▼

Yes, you can use this workflow for cross-task dependency planning. The Skill specifies dependency planning as part of Phase 2 elicitation, mapping connections to Phase 3 handoff and ensuring the URD aligns with the broader product development workflow.