What problem does it solve? Requirements projects often fail because stakeholder needs are gathered informally, from a single source, or never confirmed, leading to biased or incomplete requirements. This Skill structures the elicitation step of the Requirements Management cycle so needs are discovered with appropriate techniques and validated with stakeholders before analysis begins. ## Core Features & Use Cases - Technique Selection Guidance: Provides a decision tree and comparison of 7 elicitation techniques (interviews, JAD workshops, observation, surveys, prototypes, document analysis, benchmarking) with protocols, advantages, and limitations. - Structured Elicitation Report: Generates an rm-elicitation.md artifact from a template covering the plan, session findings, candidate requirements, conflicts, and stakeholder confirmation. - Red Flag Detection: Lists warning signs of poorly executed elicitation such as single-source bias, solution-phrased requirements, and missing stakeholder confirmation. - Use Case: A business analyst starting discovery for a call center system uses this Skill to plan interviews with supervisors, shadow agents, and produce a confirmed elicitation report before moving to requirements analysis. ## Quick Start Ask the AI to run the rm-elicitation step to plan stakeholder sessions and produce a confirmed elicitation report for the current work package.
