stakeholder-simulation

# Stakeholder Simulation Skill

Multi-persona stakeholder simulation for generating diverse requirements perspectives when working solo.

## When to Use This Skill

**Keywords:** stakeholder simulation, persona, solo elicitation, simulate stakeholder, multi-perspective, no stakeholder access, solo mode, proxy stakeholder

Invoke this skill when:

- Working without direct stakeholder access
- Need diverse perspectives on requirements
- Validating completeness of requirements
- Exploring edge cases and conflicts
- Solo developer needing stakeholder proxy

## Available Personas

| Persona | Agent | Perspective |
|---------|-------|-------------|
| End User | `end-user-persona` | Usability, UX, accessibility, daily workflows |
| Technical | `technical-stakeholder` | Architecture, scalability, security, performance |
| Business | `business-stakeholder` | ROI, market fit, value proposition, cost |
| Compliance | `compliance-stakeholder` | Regulatory, legal, audit, data protection |
| Operations | `operations-stakeholder` | Deployment, monitoring, maintenance, support |

## Simulation Modes

### Single Persona Mode

Simulate one specific stakeholder perspective:

```yaml
mode: single
persona: technical
focus: "security concerns for payment processing"
output: requirements from technical perspective
```

### Multi-Persona Mode

Run multiple personas for diverse perspectives:

```yaml
mode: multi
personas: [end-user, technical, business]
topic: "checkout redesign"
output: consolidated requirements with attributed perspectives
```

### Conflict Detection Mode

Specifically look for conflicts between stakeholder perspectives:

```yaml
mode: conflict
personas: all
topic: "feature prioritization"
output: identified conflicts with resolution suggestions
```

## Workflow

### Step 1: Context Setting

Establish the domain and topic for simulation:

```yaml
simulation_context:
  domain: "{domain name}"
  topic: "{specific topic or feature}"
  existing_requirements: "{path to existin