survey

What this skill does

# Survey Command

Generate requirements surveys and analyze stakeholder responses for data-driven elicitation.

## Usage

```bash
/requirements-elicitation:survey
/requirements-elicitation:survey --domain "checkout"
/requirements-elicitation:survey --domain "auth" --mode generate --type kano
/requirements-elicitation:survey --domain "search" --mode analyze
/requirements-elicitation:survey --domain "onboarding" --mode both --respondents 50
```

## Arguments

| Argument | Required | Description |
|----------|----------|-------------|
| --domain | No | Domain for the survey (default: current/most recent) |
| --mode | No | Mode: `generate`, `analyze`, `both` (default: `both`) |
| --type | No | Survey type: `kano`, `satisfaction`, `priority`, `discovery` (default: `discovery`) |
| --respondents | No | Expected number of respondents for analysis (default: 20) |

## Survey Types

### Discovery Survey

General-purpose requirements discovery questionnaire.

```yaml
discovery_survey:
  purpose: "Identify needs, pain points, and desired outcomes"

  sections:
    demographics:
      - "What is your role?"
      - "How often do you use [system]?"
      - "How long have you been a user?"

    current_experience:
      - "Rate your overall satisfaction (1-10)"
      - "What tasks do you perform most frequently?"
      - "What frustrates you most about the current process?"

    needs_and_goals:
      - "What are you trying to accomplish?"
      - "What prevents you from achieving your goals?"
      - "What would make your job easier?"

    feature_preferences:
      - "Which features do you use most?"
      - "Which features do you never use?"
      - "What features are missing?"

    open_ended:
      - "If you could change one thing, what would it be?"
      - "Describe your ideal experience"
      - "Any other feedback?"
```

### Kano Survey

Classify features using Kano methodology.

```yaml
kano_survey:
  purpose: "Classify features as Basic, Performance, or Excitement"

  question_pairs:
    functional:
      prompt: "If [feature] was present, how would you feel?"
      options:
        - "I would like it"
        - "I expect it"
        - "I'm neutral"
        - "I can tolerate it"
        - "I dislike it"

    dysfunctional:
      prompt: "If [feature] was absent, how would you feel?"
      options:
        - "I would like it"
        - "I expect it"
        - "I'm neutral"
        - "I can tolerate it"
        - "I dislike it"

  classification_matrix:
    "Like + Dislike": "Excitement (Delighter)"
    "Like + Neutral": "Excitement"
    "Expect + Dislike": "Basic (Must-Be)"
    "Expect + Neutral": "Performance"
    "Neutral + Neutral": "Indifferent"
    "Dislike + Like": "Reverse"
```

### Satisfaction Survey

Measure satisfaction with current/proposed features.

```yaml
satisfaction_survey:
  purpose: "Gauge satisfaction levels and identify improvement areas"

  scales:
    likert_5:
      - "Strongly Disagree"
      - "Disagree"
      - "Neutral"
      - "Agree"
      - "Strongly Agree"

    satisfaction_10:
      range: "1-10"
      anchors:
        1: "Extremely Dissatisfied"
        5: "Neutral"
        10: "Extremely Satisfied"

    nps:
      question: "How likely are you to recommend [product] to a colleague?"
      range: "0-10"
      categories:
        promoters: "9-10"
        passives: "7-8"
        detractors: "0-6"

  question_categories:
    - "Overall satisfaction"
    - "Feature-specific satisfaction"
    - "Ease of use"
    - "Performance"
    - "Reliability"
    - "Support quality"
```

### Priority Survey

Rank and prioritize features or requirements.

```yaml
priority_survey:
  purpose: "Gather stakeholder input on requirement priorities"

  methods:
    forced_ranking:
      instruction: "Rank these features from most to least important"
      output: "Ordered list by preference"

    pairwise_comparison:
      instruction: "For each pair, select the more important option"
      output: "Win/loss matrix and composite ranking"

    allocation:
      instruction: "You have 100 points. Allocate to features by importance"
      output: "Point distribution showing relative priority"

    moscow_voting:
      instruction: "Classify each feature as Must/Should/Could/Won't"
      options:
        - "Must Have"
        - "Should Have"
        - "Could Have"
        - "Won't Have (this time)"
```

## Workflow

### Generate Mode

```yaml
generate_workflow:
  1. Load domain context from .requirements/{domain}/
  2. Identify survey objectives based on elicitation stage
  3. Select appropriate survey type
  4. Generate questions tailored to domain
  5. Add demographic and contextual questions
  6. Output survey template in multiple formats
```

### Analyze Mode

```yaml
analyze_workflow:
  1. Load response data from .requirements/{domain}/surveys/
  2. Validate response completeness
  3. Perform statistical analysis
  4. Identify patterns and themes
  5. Generate requirement candidates from findings
  6. Output analysis report with visualizations
```

### Both Mode (Default)

```yaml
both_workflow:
  1. Generate survey (if not exists)
  2. Simulate/collect responses (interactive or file input)
  3. Analyze responses
  4. Generate comprehensive report
```

## Output Formats

### Survey Template

```yaml
survey_template:
  metadata:
    domain: "{domain}"
    type: "discovery"
    version: "1.0"
    created: "{ISO-8601}"

  introduction:
    title: "Requirements Survey: {domain}"
    description: "Help us understand your needs for {domain} improvements"
    estimated_time: "10-15 minutes"
    confidentiality: "Responses are anonymous and confidential"

  sections:
    - id: "S1"
      title: "About You"
      questions:
        - id: "Q1"
          type: "single_choice"
          text: "What is your primary role?"
          options:
            - "End User"
            - "Manager"
            - "Administrator"
            - "Developer"
            - "Other"
          required: true

        - id: "Q2"
          type: "scale"
          text: "How often do you use {system}?"
          scale:
            min: 1
            max: 5
            labels:
              1: "Rarely"
              3: "Weekly"
              5: "Daily"

    - id: "S2"
      title: "Current Experience"
      questions:
        - id: "Q3"
          type: "open_text"
          text: "What is your biggest challenge with the current process?"
          max_length: 500

        - id: "Q4"
          type: "multi_choice"
          text: "Which features do you use most? (Select up to 3)"
          options: [...features from domain context...]
          max_selections: 3

  closing:
    thank_you: "Thank you for your valuable feedback!"
    next_steps: "We will analyze responses and share findings within 2 weeks."
```

### Analysis Report

```yaml
analysis_report:
  metadata:
    domain: "{domain}"
    survey_type: "discovery"
    analysis_date: "{ISO-8601}"
    responses_analyzed: 47
    response_rate: "78%"

  demographics:
    role_distribution:
      end_user: 60%
      manager: 25%
      administrator: 10%
      other: 5%
    usage_frequency:
      daily: 45%
      weekly: 35%
      monthly: 15%
      rarely: 5%

  quantitative_results:
    satisfaction_scores:
      overall: 6.2
      ease_of_use: 5.8
      performance: 7.1
      reliability: 6.5

    nps_score: 32
    nps_breakdown:
      promoters: 45%
      passives: 30%
      detractors: 25%

    feature_priorities:
      - feature: "Real-time tracking"
        priority_score: 8.7
        mentions: 38
      - feature: "Mobile access"
        priority_score: 8.2
        mentions: 34

  qualitative_analysis:
    themes:
      - theme: "Speed and Performance"
        frequency: 28
        sentiment: "negative"
        sample_quotes:
          - "The system is too slow during peak hours"
          - "Loading times are frustrating"

      - theme: "Mobile Experience"
        frequency: 22
        sentiment: "mixed"
        sample_