gvm-requirements

Requirements elicitation for a new feature uses adaptive conversation and expert techniques to gather and structure implementation-agnostic software requirements, ensuring thorough coverage through automated change detection and cross-cutting item handling.

Requirements gathering handles cross-cutting items by tracking assumptions, open questions, out-of-scope items, and source verification for external document seeds. This ensures all implicit project boundaries are explicitly documented during the elicitation process.

Finalizing requirements with MoSCoW prioritization confirms priority categories, generates a requirements index table, and ensures HTML and MD synchronization. This finalization step produces a comprehensive, structured requirements document ready for implementation.

Expert elicitation techniques for GVM methodology projects are fully supported, automatically detecting the project pipeline state and adapting the elicitation process accordingly to ensure requirements align with the structured GVM framework.

Gathering requirements from external documents uses source verification to seed the elicitation process. The adaptive conversation then extracts, refines, and structures the information while automatically detecting pipeline state changes to adapt the workflow.