skills/multi-perspective-analysis/SKILL.md
Adopt multiple expert personas sequentially for complex problem analysis from diverse perspectives. Single-agent only — do NOT spawn sub-agents.
npx skillsauth add nickcrew/claude-cortex multi-perspective-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Adopt multiple expert personas sequentially to analyze complex problems from diverse perspectives, generating insights unavailable from any single viewpoint.
You are a single agent who adopts different expert perspectives one at a time. Do NOT use the Task tool. Do NOT spawn sub-agents, teammates, or parallel workers. Each "expert" is a lens you look through — not a separate process.
The orchestration patterns below describe the ORDER in which you adopt perspectives, not a delegation strategy. "Parallel" means you analyze independently from each perspective before synthesizing — not that multiple agents run simultaneously.
| Complexity | Perspectives | Structure | |------------|-------------|-----------| | Simple | 3-4 | Single pass through each, then synthesize | | Moderate | 5-6 | Two passes (initial + challenge round), then synthesize | | Complex | 7-9 | Group into layers, synthesize per layer, then overall |
## [Problem Domain] Perspectives
**Mission**: [Clear statement of analysis purpose]
### Perspectives
#### [Expert Title]
**Background**: [Relevant expertise you adopt]
**Domain Vocabulary**: [5-7 key terms to use in this lens]
**Characteristic Question**: "[What this persona always asks]"
**Analytical Lens**: [Unique perspective this persona brings]
These describe the order in which YOU adopt each perspective. You are one agent switching lenses — not multiple agents running in parallel.
Best for: Problems with clear dependency chains
Adopt Perspective A → Adopt Perspective B → Adopt Perspective C → Synthesize
(Each perspective builds on insights from the previous one)
Best for: Problems needing diverse unbiased perspectives
Adopt Perspective A (record findings)
Adopt Perspective B (record findings, don't reference A's)
Adopt Perspective C (record findings, don't reference A's or B's)
→ Synthesize all findings together
Best for: Problems with competing valid approaches
Adopt Perspective A (thesis) → Adopt Perspective B (challenge A's findings)
→ Synthesize the tension into a resolution
Best for: Complex multi-level decisions
Adopt strategic perspectives (A, B) → synthesize strategic layer
Adopt tactical perspectives (C, D, E) → synthesize tactical layer
Adopt operational perspectives (F, G) → synthesize operational layer
→ Final synthesis across all layers
Each expert maintains distinct:
### [Expert Title] Perspective
Adopting the lens of a [role], I notice...
**Key Insight**: [Primary contribution from this perspective]
**Trade-off Identified**: [What this view reveals about tensions]
**Recommendation**: [Actionable guidance from this expertise]
**Next Question**: [What this reveals we should explore]
Gentle (refinement-focused)
Systematic (methodology-challenging)
Rigorous (premise-challenging)
Paradigmatic (worldview-challenging)
## Multi-Perspective Synthesis
### Convergent Insights
[Where experts agree and why this matters]
### Creative Tensions
[Where perspectives productively differ]
- Tension 1: [Expert A] vs [Expert B] on [issue]
- Resolution approach: [How to honor both]
### Integrated Solution
[Unified approach that honors multiple viewpoints]
### Emergent Discoveries
[Insights that emerged only from combining perspectives]
### Implementation Path
1. [First action]
2. [Second action]
3. [Third action]
development
Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.
development
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
development
Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.
tools
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.