Simulates End User, Technical, Business, Compliance, and Operations personas to generate diverse requirements perspectives for solo developers without stakeholder access.
How this skill is triggered — by the user, by Claude, or both
Slash command
/requirements-elicitation:stakeholder-simulationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Multi-persona stakeholder simulation for generating diverse requirements perspectives when working solo.
Multi-persona stakeholder simulation for generating diverse requirements perspectives when working solo.
Keywords: stakeholder simulation, persona, solo elicitation, simulate stakeholder, multi-perspective, no stakeholder access, solo mode, proxy stakeholder
Invoke this skill when:
| 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 |
Simulate one specific stakeholder perspective:
mode: single
persona: technical
focus: "security concerns for payment processing"
output: requirements from technical perspective
Run multiple personas for diverse perspectives:
mode: multi
personas: [end-user, technical, business]
topic: "checkout redesign"
output: consolidated requirements with attributed perspectives
Specifically look for conflicts between stakeholder perspectives:
mode: conflict
personas: all
topic: "feature prioritization"
output: identified conflicts with resolution suggestions
Establish the domain and topic for simulation:
simulation_context:
domain: "{domain name}"
topic: "{specific topic or feature}"
existing_requirements: "{path to existing requirements if any}"
autonomy_level: guided|semi-auto|full-auto
Determine which personas to simulate:
All Personas (comprehensive):
Selected Personas (focused):
For each selected persona, spawn the corresponding agent:
simulation_execution:
- persona: end-user
agent: end-user-persona
prompt: "From an end user perspective, what requirements would you have for {topic}?"
- persona: technical
agent: technical-stakeholder
prompt: "What technical requirements and constraints exist for {topic}?"
Collect requirements from each persona:
collected_requirements:
- id: REQ-SIM-001
text: "{requirement statement}"
persona: "{which persona generated this}"
perspective: "{user|technical|business|compliance|operations}"
priority: must|should|could
confidence: medium # Always medium for simulated
rationale: "{why this requirement matters to this persona}"
Identify conflicts between perspectives:
conflicts:
- id: CONFLICT-001
requirements: [REQ-SIM-003, REQ-SIM-012]
description: "End user wants simplicity; Technical wants security"
personas: [end-user, technical]
suggested_resolution: "{proposed compromise}"
Merge and deduplicate requirements:
consolidated:
- id: REQ-SIM-FINAL-001
text: "{consolidated requirement}"
supported_by: [end-user, business]
priority: must
confidence: medium
needs_validation: true # All simulated requirements need validation
Perspective: Daily user experience
Focuses On:
Typical Questions:
Perspective: System architecture and implementation
Focuses On:
Typical Questions:
Perspective: Business value and market fit
Focuses On:
Typical Questions:
Perspective: Regulatory and legal requirements
Focuses On:
Typical Questions:
Perspective: Deployment and ongoing operations
Focuses On:
Typical Questions:
simulation_results:
session_id: "SIM-{timestamp}"
domain: "{domain}"
topic: "{topic}"
personas_simulated: [end-user, technical, business]
autonomy_level: semi-auto
requirements_by_persona:
end-user:
count: 8
requirements:
- id: REQ-SIM-EU-001
text: "Login should take less than 3 clicks"
priority: should
rationale: "Reduces friction in daily workflow"
technical:
count: 6
requirements:
- id: REQ-SIM-TEC-001
text: "System must support OAuth 2.0 + MFA"
priority: must
rationale: "Security best practice"
conflicts_detected:
- personas: [end-user, technical]
issue: "Simplicity vs security trade-off"
eu_position: "Fewer steps"
tech_position: "MFA required"
resolution: "Implement remember-device option"
consolidated_requirements:
total: 18
by_priority:
must: 6
should: 8
could: 4
validation_needed:
- All simulated requirements should be validated with real stakeholders
- Conflicts flagged for human decision
IMPORTANT: All simulated requirements have:
medium (never high)needs_validation: trueSimulation provides perspectives but cannot replace real stakeholder input. Always flag simulated requirements for validation when stakeholders become available.
For related tasks:
Save simulation results to:
.requirements/{domain}/simulations/SIM-{timestamp}.yaml
elicitation-methodology - Parent hub skillinterview-conducting - Real stakeholder interviewsgap-analysis - Post-simulation completeness checkingnpx claudepluginhub melodic-software/claude-code-plugins --plugin requirements-elicitationSimulates end-user, technical, business, compliance, and operations stakeholders to generate requirements for features, systems, or topics. Supports standard, conflict, and comprehensive modes.
Conducts simulated user interviews via diverse personas (founder-twin, adversarial, etc.) for solo/hobby/dogfood projects, enforcing anti-bias discipline like pre-defined spectra and stop conditions.
Analyzes decisions from engineering, product, legal, finance, and user perspectives to surface tensions and find alignment. Use when stakeholders have conflicting priorities.