# Stakeholder Requirement Mapping

> Translate cross-department needs into unified requirements. Use when requirements from sales/ops/finance, cross-department needs, stakeholder alignment, or conflicting requirements.

- Skill: `uwayxt/stakeholder-requirement-mapping` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add uwayxt/stakeholder-requirement-mapping`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uwayxt/stakeholder-requirement-mapping/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: Uwayxt (https://skillmd.com/u/uwayxt)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/uwayxt/stakeholder-requirement-mapping

---


# Stakeholder Requirement Mapping

**Every department speaks a different language about the same product. This skill translates, deduplicates, and resolves conflicts before they become architecture problems.**

### 1. Map stakeholders
Who has a stake? List every department or role that will touch the product (sales, ops, finance, customer support, legal, end users). Detail what they need from the product and why.

### 2. Extract requirements per stakeholder
Separate stated needs ("I want a report") from underlying needs ("I need to know which customers are at risk of churning"). Underlying needs survive requirements changes; stated needs don't.

### 3. Cross-reference and deduplicate
Merge duplicates where multiple stakeholders ask for the same thing in different words. Surface contradictions explicitly ("Sales wants unlimited free trials; Finance wants paid-only access").

### 4. Resolve conflicts
Propose resolution for each contradiction. Escalate to the user for unresolvable conflicts. Record the decision and rationale.

### 5. Produce unified requirement list
Map each requirement to originating stakeholder(s), priority, and resolution status.

### Completion Criteria
Done when all stakeholder inputs are mapped, deduplicated, and all direct conflicts are resolved or escalated.

### Output Format
Stakeholder Map and Requirements Matrix (requirement → stakeholder → priority → status).