autonomy: guided
behavior:
  - AI suggests questions, human approves
  - Each requirement validated individually
  - Human controls interview flow
  - Maximum transparency
use_when:
  - Sensitive or regulated domains
  - Learning the elicitation process
  - High-stakes requirements

autonomy: semi-auto
behavior:
  - AI conducts interviews with checkpoints
  - Human validates requirement batches
  - Periodic progress reviews
  - Balance of speed and control
use_when:
  - Standard elicitation projects
  - Moderate domain complexity
  - Trusted AI capabilities

autonomy: full-auto
behavior:
  - Complete end-to-end elicitation
  - Human reviews final output only
  - Maximum efficiency
  - AI handles all decisions
use_when:
  - Well-understood domains
  - Time pressure
  - Preliminary discovery

1. CONTEXT GATHERING
   ├── Load any existing business context
   ├── Identify available sources (stakeholders, docs, etc.)
   └── Select autonomy level

2. MULTI-SOURCE ELICITATION
   ├── Interviews (if stakeholders available)
   ├── Document extraction (if docs available)
   ├── Domain research (MCP queries)
   └── Stakeholder simulation (if solo mode)

3. SYNTHESIS
   ├── Consolidate requirements from all sources
   ├── Remove duplicates
   ├── Classify by type (functional, NFR, constraint)
   └── Apply MoSCoW prioritization

4. VALIDATION
   ├── Gap analysis
   ├── Completeness checking
   ├── Conflict detection
   └── INVEST scoring

5. OUTPUT
   ├── Save to .requirements/{domain}/
   ├── Generate summary report
   └── Prepare for specification export

# .requirements/{domain}/requirements.yaml
id: REQ-SET-{number}
title: "{Domain} Requirements"
domain: "{domain-name}"
elicitation_date: "{ISO-8601-date}"
autonomy_level: "{guided|semi-auto|full-auto}"

sources:
  - type: interview|document|simulation|research
    reference: "{source-identifier}"
    timestamp: "{ISO-8601-date}"

requirements:
  - id: REQ-{number}
    text: "{requirement statement}"
    source: "{source-type}"
    source_ref: "{specific-reference}"
    priority: must|should|could|wont
    category: functional|non-functional|constraint|assumption
    confidence: high|medium|low
    validation_status: pending|validated|rejected

gaps_identified:
  - category: "{requirement-category}"
    description: "{what's missing}"
    severity: critical|major|minor

metadata:
  total_sources: {number}
  total_requirements: {number}
  gap_count: {number}
  ready_for_specification: true|false

/requirements-elicitation:export --to canonical  # Canonical spec format
/requirements-elicitation:export --to ears       # EARS pattern format
/requirements-elicitation:export --to gherkin    # Gherkin/BDD format