Assembles 3-10 specialized personas to multi-perspective analyze problems via split-team framework, facilitates productive disagreement, and synthesizes actionable insights.
From personalitiesnpx claudepluginhub dotclaude/marketplace --plugin personalities<problem-or-question> [complexity-level] [perspective-count]sonnet/analyzeAnalyzes project code across quality, security, performance, and architecture domains, producing severity-rated findings, actionable recommendations, metrics, and reports.
/analyzeAnalyzes repository code health via complexity metrics, git churn, and test coverage. Generates report with overview, critical issues, warnings, recommendations.
/analyzeInteractively analyzes marketing campaign performance: configures scope, period, type, metrics focus via questions; provides insights, optimizations, and ROI attribution.
/analyzeAnalyzes stock ticker fundamentals, news, price action, institutional holders, and delivers valuation, risks, catalysts, and investment recommendation.
/analyzeScans codebase for features, components, APIs, and models; interviews user for business context; generates and saves product inventory and architecture reports to .pm/.
/analyzeAnalyzes Rails codebase or directory for layered architecture adherence, mapping layers, assessing services, detecting model violations, god objects, and abstraction opportunities.
Orchestrate sophisticated multi-perspective analysis of problems using the split-team framework. Assemble optimal persona teams, facilitate cognitive harmonics, and synthesize insights through productive disagreement.
This command invokes the persona-coordinator agent to:
$1 (Required): Problem statement or question to analyze
$2 (Optional): Complexity level
simple: 3-4 personas, straightforward analysismoderate: 5-6 personas, balanced trade-offs (default)complex: 7+ personas, multifaceted challenges$3 (Optional): Number of personas (3-10)
/analyze "Should we use REST or GraphQL for our API?" simple
Assembles: Analytical Thinker + Pragmatic Realist + Systems Architect
/analyze "Design an authentication system for our platform"
Assembles: Systems Architect + Risk Analyst + User Advocate + Pragmatic Realist + Constructive Critic
/analyze "Should we migrate from monolith to microservices?" complex
Assembles: Systems Architect + Risk Analyst + Pragmatic Realist + Creative Innovator + Constructive Critic + User Advocate + Analytical Thinker
/analyze "Evaluate our tech stack choices" moderate 6
Assembles: 6 most relevant personas for the problem
Architecture Decisions
Product Strategy
Technical Challenges
Strategic Planning
Voice Differentiation: Each persona maintains unique vocabulary, questions, and analytical approach
Cognitive Harmonics: Multiple perspectives create constructive interference for emergent insights
Productive Disagreement: Systematic challenge strengthens solutions and prevents groupthink
Integration Synthesis: Coordinator weaves perspectives into coherent, actionable guidance
/analyze "We need to choose between PostgreSQL and MongoDB for user data storage. We have 10M users, need strong consistency, but want flexibility for future features." moderate
Result: Assembles 5 personas who examine through data/performance (Analytical Thinker), implementation reality (Pragmatic Realist), system architecture (Systems Architect), risk factors (Risk Analyst), and challenges assumptions (Constructive Critic). Synthesis provides clear recommendation with rationale and acknowledged trade-offs.
Invoke the persona-coordinator agent with: $ARGUMENTS