requirements-elicitation

Structured requirement elicitation uses a 9-dimension questionnaire workflow to systematically gather business requirements before implementation. It covers business context, process workflows, data models, validation rules, and acceptance criteria to reach stakeholder consensus.

The best way to document stakeholder requirements for handoff is to maintain a traceable Q&A history across rounds with per-round summaries and synthesis analysis. This preserves a complete trace of all questions and answers for downstream planning skills.

You need a structured requirement elicitation workflow whenever a user proposes a new requirement, feature, change request, or business need. It acts as a senior business analyst to read existing materials and ask dimension-by-dimension questions before any implementation begins.

Auto-routing works when a risk-classifier identifies P0 or P1 single-domain requirements and automatically routes them to this elicitation workflow. The process ensures alignment with session-state and risk tier while orchestrating escalation of critical issues when needed.

You should cover 9 dimensions when gathering business requirements: Business & Context, Process & Workflow, Data Model & State, Business Rules & Validation, Inventory & Resources, Edge Cases & Error Handling, Migration & Compatibility, Business Scenarios, and Acceptance Criteria.

You can use requirement elicitation completely standalone by directly prompting the 9-dimension questionnaire, or it can be auto-routed by a risk-classifier for high-risk items. It operates independently without requiring external dependencies to function.