gaia-advanced-elicitation

Document hidden requirements and stakeholder needs via guided elicitation interviews and analysis into a dated report.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-advanced-elicitation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-advanced-elicitation
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-advanced-elicitation
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-advanced-elicitation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This elicitation workflow helps teams uncover missing requirements by guiding structured interviewing and analysis across stakeholders and contexts.

Core Features & Use Cases

  • Guided methods: 5 Whys, Socratic Method, User Story Mapping, MoSCoW, Kano Model, Jobs-To-Be-Done.
  • Stimulates stakeholder alignment and requirement traceability across the product lifecycle.
  • Use Case: When starting a new feature, run a guided elicitation to surface hidden needs and validate assumptions.

Quick Start

Describe the initial product goal and constraints, then begin the elicitation session to generate the structured requirements report.

Frequently Asked Questions about gaia-advanced-elicitation

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

FAQPage Schema
What is requirements elicitation and when do I need structured stakeholder interviewing?

Requirements elicitation uncovers hidden stakeholder needs through structured questioning. You need it when starting new features to validate assumptions, surface missing requirements, and align stakeholders across the product lifecycle.

How do I elicit hidden requirements using the 5 Whys and Socratic method?

Elicit hidden requirements by applying guided methods like 5 Whys and Socratic method to structure stakeholder interviews. The workflow guides context gathering, method selection, and synthesis to produce traceable elicitation outputs.

How do I prioritize requirements using MoSCoW and the Kano Model during elicitation?

Prioritize requirements by applying MoSCoW and Kano Model frameworks during elicitation sessions. These guided methods categorize features by necessity and stakeholder satisfaction, ensuring structured prioritization within the elicitation report.

Can I use user story mapping and Jobs-To-Be-Done for requirement traceability across product development?

User story mapping and Jobs-To-Be-Done are supported elicitation methods that stimulate stakeholder alignment and ensure requirement traceability across diverse product development contexts.

What's the best way to document elicitation results for stakeholder alignment?

Document elicitation results by generating a structured elicitation report at docs/planning-artifacts/elicitation-report-{date}.md. This enforces a repeatable workflow with traceable outputs synthesized from diverse stakeholder perspectives.

Why does my requirements elicitation process fail to surface hidden stakeholder needs?

Elicitation fails to surface hidden needs when lacking structured context gathering and method selection. Applying Socratic method, 5 Whys, and diverse perspective synthesis enforces a repeatable workflow that reveals underlying assumptions.