stakeholder-analysis
Installation
SKILL.md
Purpose
Systematically identify all stakeholders and user classes for a software project, classify them by type and influence, and establish appropriate engagement strategies. Use this to avoid the costly mistake of discovering a key stakeholder late in the project, to resolve conflicting requirements by understanding each group's priorities, and to ensure the right people are involved at the right time.
This is not a simple contact list -- it is an analytical framework that drives who you talk to, whose needs take priority, and how conflicts get resolved.
Key Concepts
Stakeholder Categories
Not all stakeholders are equal. Classify them by relationship to the system:
- Users -- People who directly interact with the system
- Customers -- People who purchase or commission the system (may not be users)
- Sponsors -- People who fund and authorize the project
- Domain experts -- Subject matter experts who understand the business rules
- Regulators -- External parties imposing compliance constraints
- Maintainers -- People who will operate and maintain the system post-launch