Help us improve
Share bugs, ideas, or general feedback.
From code-quality
Use when user needs multi-stakeholder analysis, business impact assessment, or wants perspectives from different roles. Triggers on: "analyze from business perspective", "what would stakeholders think", "impact analysis", "business case for", "ROI of"
npx claudepluginhub wgordon17/personal-claude-marketplace --plugin code-qualityHow this skill is triggered — by the user, by Claude, or both
Slash command
/code-quality:business-panelThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Simulates perspectives from different organizational roles to provide comprehensive business impact analysis.
Runs a multi-phase verification pipeline for Laravel projects: environment checks, Composer validation, linting (Pint), static analysis (PHPStan/Psalm), tests with coverage, security audit (Composer audit), migration review, build readiness (config/route/view cache), and queue/scheduler checks.
Share bugs, ideas, or general feedback.
Simulates perspectives from different organizational roles to provide comprehensive business impact analysis.
Simulate perspectives from these roles:
Focus Areas:
Key Questions:
Focus Areas:
Key Questions:
Focus Areas:
Key Questions:
Focus Areas:
Key Questions:
Focus Areas:
Key Questions:
Focus Areas:
Key Questions:
| Stakeholder | Impact Level | Key Concerns | Benefits | Risks |
|-------------|--------------|--------------|----------|-------|
| CTO | High | [List] | [List] | [List] |
| Product | Medium | [List] | [List] | [List] |
| Engineering | High | [List] | [List] | [List] |
| Finance | Medium | [List] | [List] | [List] |
| Security | Low | [List] | [List] | [List] |
| Operations | High | [List] | [List] | [List] |
| Category | Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|---|
| Technical | [Risk] | H/M/L | H/M/L | [Action] |
| Business | [Risk] | H/M/L | H/M/L | [Action] |
| Operational | [Risk] | H/M/L | H/M/L | [Action] |
| Security | [Risk] | H/M/L | H/M/L | [Action] |
| Compliance | [Risk] | H/M/L | H/M/L | [Action] |
## Initial Investment
| Item | One-Time Cost | Notes |
|------|---------------|-------|
| Development | $X | [hours × rate] |
| Infrastructure | $X | [setup costs] |
| Training | $X | [team upskilling] |
| **Total Initial** | **$X** | |
## Ongoing Costs (Annual)
| Item | Annual Cost | Notes |
|------|-------------|-------|
| Maintenance | $X | [hours × rate] |
| Infrastructure | $X | [hosting, licenses] |
| Support | $X | [vendor, on-call] |
| **Total Annual** | **$X** | |
## Expected Benefits (Annual)
| Benefit | Annual Value | Notes |
|---------|--------------|-------|
| Time savings | $X | [hours saved × rate] |
| Revenue impact | $X | [new revenue or retained] |
| Risk reduction | $X | [avoided incident costs] |
| **Total Annual** | **$X** | |
## ROI Calculation
- **Payback Period**: X months
- **3-Year ROI**: X%
- **NPV (5% discount)**: $X
## Recommendation: [APPROVE / DEFER / REJECT]
### Summary
[2-3 sentence summary of recommendation and key reasoning]
### Key Factors For
1. [Factor 1 with supporting evidence]
2. [Factor 2 with supporting evidence]
3. [Factor 3 with supporting evidence]
### Key Factors Against
1. [Factor 1 with supporting evidence]
2. [Factor 2 with supporting evidence]
### Conditions for Success
- [Condition 1 that must be true for this to succeed]
- [Condition 2]
### Key Assumptions
- [Assumption 1 that the analysis depends on]
- [Assumption 2]
### Review Triggers
- Revisit this decision if:
- [Trigger 1: e.g., costs exceed budget by 20%]
- [Trigger 2: e.g., key team member leaves]
- [Trigger 3: e.g., market conditions change]
# Business Panel Analysis: [Decision/Topic]
## Executive Summary
[3-4 sentence summary of the decision, key stakeholder perspectives, and recommendation]
## Decision Context
- **What we're deciding**: [Clear statement]
- **Why now**: [Urgency or trigger]
- **Alternatives considered**: [Brief list]
## Stakeholder Perspectives
### CTO View
**Position**: [Support/Oppose/Neutral]
**Key Points**:
- [Point 1]
- [Point 2]
**Concerns**: [What worries this stakeholder]
### Product View
**Position**: [Support/Oppose/Neutral]
**Key Points**:
- [Point 1]
- [Point 2]
**Concerns**: [What worries this stakeholder]
[...repeat for each stakeholder...]
## Impact Analysis
### Stakeholder Impact Matrix
[See template above]
### Risk Assessment
[See template above]
### Cost-Benefit Analysis
[See template above]
## Consensus & Disagreement
### Points of Agreement
- [What all stakeholders agree on]
### Points of Disagreement
- **Issue**: [Description]
- **CTO view**: [Position]
- **Finance view**: [Position]
- **Resolution**: [How to resolve or who decides]
## Recommendation
[See template above]
## Next Steps
1. [Immediate action with owner]
2. [Short-term action with owner and deadline]
3. [Follow-up checkpoint with criteria]
Before simulating panel perspectives, check whether the analysis involves:
If any apply, invoke /deep-research (via the Skill tool) before proceeding to Step 3 —
use External mode for pure market/technology questions, or Bridged mode when the analysis
involves a technology the project already uses. Pass the analysis topic as the research
question. The research report will be saved to {memory_dir}/research/ (if a memory
directory exists).