stakeholder-preference-elicitor

Stakeholder preference elicitation skill for structured value and weight gathering

509 stars

Best use case

stakeholder-preference-elicitor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Stakeholder preference elicitation skill for structured value and weight gathering

Teams using stakeholder-preference-elicitor should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/stakeholder-preference-elicitor/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/domains/business/decision-intelligence/skills/stakeholder-preference-elicitor/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/stakeholder-preference-elicitor/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How stakeholder-preference-elicitor Compares

Feature / Agentstakeholder-preference-elicitorStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Stakeholder preference elicitation skill for structured value and weight gathering

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Stakeholder Preference Elicitor

## Overview

The Stakeholder Preference Elicitor skill provides structured methods for gathering value judgments and weights from decision stakeholders. It supports multiple elicitation techniques, consistency checking, and preference aggregation for group decisions.

## Capabilities

- Swing weight elicitation
- Direct rating collection
- Trade-off questioning
- Consistency checking
- Preference aggregation
- Disagreement identification
- Facilitation guidance
- Preference documentation

## Used By Processes

- Multi-Criteria Decision Analysis (MCDA)
- Structured Decision Making Process
- KPI Framework Development

## Usage

### Elicitation Session Setup

```python
# Configure elicitation session
session_config = {
    "decision": "Enterprise Software Selection",
    "criteria": [
        {"name": "Total Cost of Ownership", "unit": "USD", "direction": "minimize"},
        {"name": "Implementation Time", "unit": "months", "direction": "minimize"},
        {"name": "Functionality Fit", "unit": "percent", "direction": "maximize"},
        {"name": "Vendor Stability", "unit": "score", "direction": "maximize"},
        {"name": "Integration Capability", "unit": "score", "direction": "maximize"}
    ],
    "stakeholders": [
        {"id": "S1", "name": "CIO", "role": "Decision Maker", "weight": 0.3},
        {"id": "S2", "name": "CFO", "role": "Decision Maker", "weight": 0.3},
        {"id": "S3", "name": "IT Director", "role": "Technical Expert", "weight": 0.2},
        {"id": "S4", "name": "Business Lead", "role": "User Representative", "weight": 0.2}
    ],
    "elicitation_method": "swing_weights"
}
```

### Swing Weight Elicitation

```python
# Swing weight process
swing_weight_protocol = {
    "step_1_ranges": {
        "description": "Define worst and best levels for each criterion",
        "ranges": {
            "Total Cost of Ownership": {"worst": 2000000, "best": 500000},
            "Implementation Time": {"worst": 24, "best": 6},
            "Functionality Fit": {"worst": 60, "best": 95},
            "Vendor Stability": {"worst": 3, "best": 9},
            "Integration Capability": {"worst": 2, "best": 10}
        }
    },
    "step_2_reference": {
        "description": "Imagine all criteria at worst level. Which would you most want to swing to best?",
        "responses": {
            "S1": "Functionality Fit",
            "S2": "Total Cost of Ownership",
            "S3": "Integration Capability",
            "S4": "Functionality Fit"
        }
    },
    "step_3_relative_weights": {
        "description": "If most important swing = 100, rate the value of other swings",
        "responses": {
            "S1": {
                "Functionality Fit": 100,
                "Total Cost of Ownership": 80,
                "Integration Capability": 60,
                "Implementation Time": 40,
                "Vendor Stability": 30
            }
            # ... other stakeholders
        }
    }
}
```

### Trade-off Questions

```python
# Trade-off elicitation
tradeoff_questions = {
    "format": "matching",
    "questions": [
        {
            "id": "TQ1",
            "question": "You can have software with 95% functionality fit. How much extra cost would you accept to maintain this level vs. 75% fit?",
            "criteria_pair": ["Functionality Fit", "Total Cost of Ownership"],
            "anchors": {"Functionality Fit": {"from": 75, "to": 95}}
        },
        {
            "id": "TQ2",
            "question": "Implementation in 6 months vs 12 months: how much more would you pay for the faster option?",
            "criteria_pair": ["Implementation Time", "Total Cost of Ownership"],
            "anchors": {"Implementation Time": {"from": 12, "to": 6}}
        }
    ]
}
```

### Consistency Check

```python
# Check for consistency
consistency_check = {
    "method": "transitivity",
    "checks": [
        {
            "stakeholder": "S1",
            "issue": "weight_inconsistency",
            "details": "Cost weight (80) + Fit weight (100) implies Cost > Time, but trade-off suggests otherwise",
            "severity": "warning",
            "recommendation": "Revisit cost vs. time comparison"
        }
    ],
    "overall_consistency": 0.85
}
```

### Group Aggregation

```python
# Aggregate preferences
aggregation_config = {
    "method": "weighted_geometric_mean",
    "stakeholder_weights": {"S1": 0.3, "S2": 0.3, "S3": 0.2, "S4": 0.2},
    "individual_weights": {
        "S1": {"TCO": 0.26, "Time": 0.13, "Fit": 0.32, "Stability": 0.10, "Integration": 0.19},
        "S2": {"TCO": 0.35, "Time": 0.15, "Fit": 0.25, "Stability": 0.15, "Integration": 0.10},
        # ... etc.
    },
    "aggregated_weights": {
        "TCO": 0.29,
        "Time": 0.14,
        "Fit": 0.28,
        "Stability": 0.12,
        "Integration": 0.17
    },
    "disagreement_metrics": {
        "highest_variance_criterion": "Total Cost of Ownership",
        "coefficient_of_variation": 0.15
    }
}
```

## Input Schema

```json
{
  "session_config": {
    "decision": "string",
    "criteria": ["object"],
    "stakeholders": ["object"],
    "method": "string"
  },
  "elicitation_data": {
    "method": "swing|direct|tradeoff|pairwise",
    "responses": "object"
  },
  "aggregation_config": {
    "method": "geometric_mean|arithmetic_mean|majority",
    "stakeholder_weights": "object"
  }
}
```

## Output Schema

```json
{
  "individual_weights": {
    "stakeholder_id": {
      "criterion": "number"
    }
  },
  "aggregated_weights": {
    "criterion": "number"
  },
  "consistency": {
    "individual_scores": "object",
    "issues": ["object"]
  },
  "disagreement_analysis": {
    "high_variance_criteria": ["string"],
    "stakeholder_clusters": "object",
    "discussion_points": ["string"]
  },
  "documentation": {
    "methodology": "string",
    "assumptions": ["string"],
    "limitations": ["string"]
  }
}
```

## Elicitation Methods

| Method | Best For | Complexity |
|--------|----------|------------|
| Swing Weights | Trading off criteria | Medium |
| Direct Rating | Quick assessment | Low |
| Pairwise Comparison | Systematic comparison | High |
| Trade-off | Understanding value | Medium |
| Point Allocation | Intuitive weights | Low |

## Best Practices

1. Explain criteria clearly before elicitation
2. Use concrete examples and scenarios
3. Check for consistency and discuss discrepancies
4. Allow stakeholders to revise after seeing group results
5. Document reasoning, not just numbers
6. Consider cognitive biases (anchoring, order effects)
7. Use multiple methods for important decisions

## Common Biases

| Bias | Description | Mitigation |
|------|-------------|------------|
| Anchoring | Over-reliance on first information | Randomize order |
| Availability | Weight by memorable events | Use structured data |
| Overconfidence | Narrow probability ranges | Calibration training |
| Order Effects | Influenced by question sequence | Vary order across stakeholders |

## Integration Points

- Feeds into AHP Calculator for weight processing
- Connects with MCDA Facilitator agent
- Supports Consistency Validator for quality checks
- Integrates with Decision Documentation for audit trail

Related Skills

Stakeholder Communication

509
from a5c-ai/babysitter

Generate stakeholder-specific communications and presentations for product updates

stakeholder-facilitation

509
from a5c-ai/babysitter

Facilitate meetings, workshops, and community consultations with diverse stakeholders including artists, board members, funders, and community representatives

stakeholder-crm

509
from a5c-ai/babysitter

Stakeholder relationship management and engagement tracking

stakeholder-matrix-generator

509
from a5c-ai/babysitter

Generate stakeholder analysis matrices and visualizations including Power-Interest grids and RACI matrices

process-builder

509
from a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Workflow & Productivity

babysitter

509
from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)

yolo

509
from a5c-ai/babysitter

Run Babysitter autonomously with minimal manual interruption.

user-install

509
from a5c-ai/babysitter

Install the user-level Babysitter Codex setup.

team-install

509
from a5c-ai/babysitter

Install the team-pinned Babysitter Codex workspace setup.

retrospect

509
from a5c-ai/babysitter

Summarize or retrospect on a completed Babysitter run.

resume

509
from a5c-ai/babysitter

Resume an existing Babysitter run from Codex.

project-install

509
from a5c-ai/babysitter

Install the Babysitter Codex workspace integration into the current project.