Use when stakeholders have conflicting priorities and need alignment, suspect decision blind spots from single perspective, need to pressure-test proposals before presenting, want empathy for different viewpoints (eng vs PM vs legal vs user), building consensus across functions, evaluating tradeoffs with multi-dimensional impact, or when user mentions "what would X think", "stakeholder alignment", "see from their perspective", "blind spots", or "conflicting interests".
View on GitHublyndonkl/claude
thinking-frameworks-skills
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/lyndonkl/claude/blob/main/skills/role-switch/SKILL.md -a claude-code --skill role-switchInstallation paths:
.claude/skills/role-switch/# Role Switch ## Table of Contents 1. [Purpose](#purpose) 2. [When to Use](#when-to-use) 3. [What Is It](#what-is-it) 4. [Workflow](#workflow) 5. [Role Selection Patterns](#role-selection-patterns) 6. [Synthesis Principles](#synthesis-principles) 7. [Common Patterns](#common-patterns) 8. [Guardrails](#guardrails) 9. [Quick Reference](#quick-reference) ## Purpose Role Switch helps uncover blind spots, align stakeholders, and make better decisions by systematically analyzing from multiple perspectives. It transforms single-viewpoint analysis into multi-stakeholder synthesis with explicit tradeoffs and alignment paths. ## When to Use **Invoke this skill when you need to:** - Align stakeholders with conflicting priorities (eng vs PM vs sales vs legal) - Uncover blind spots in decisions by viewing from multiple angles - Pressure-test proposals before presenting to diverse audiences - Build empathy for perspectives different from your own - Navigate cross-functional tradeoffs (cost vs quality, speed vs thoroughness) - Evaluate decisions with multi-dimensional impact (technical, business, user, regulatory) - Find consensus paths when positions seem incompatible - Validate assumptions by seeing what different roles would challenge **User phrases that trigger this skill:** - "What would [stakeholder] think about this?" - "How do we get alignment across teams?" - "I'm worried we're missing something" - "See this from their perspective" - "Conflicting priorities between X and Y" - "Stakeholder buy-in strategy" ## What Is It A structured analysis that: 1. **Identifies relevant roles** (stakeholders with different goals, constraints, incentives) 2. **Adopts each perspective** (inhabits mindset, priorities, success criteria of that role) 3. **Articulates viewpoint** (what this role cares about, fears, values, measures) 4. **Surfaces tensions** (where perspectives conflict, tradeoffs emerge) 5. **Synthesizes alignment** (finds common ground, proposes resolutions, sequences