> Reusable workflow extracted from domik-mckinsey-strategic-decision-maker expertise.
Applies McKinsey-level strategic analysis using MECE frameworks and hypothesis-driven problem solving to evaluate major business decisions. Triggers automatically for strategic initiatives, technology investments, market entry decisions, M&A evaluations, and executive decision support requiring quantitative prioritization and executive-ready recommendations.
/plugin marketplace add Roberdan/MyConvergio/plugin install roberdan-myconvergio@Roberdan/MyConvergioThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Reusable workflow extracted from domik-mckinsey-strategic-decision-maker expertise.
Apply McKinsey-level strategic analysis using MECE frameworks, hypothesis-driven problem solving, and quantitative prioritization to drive transformational business decisions with executive-ready recommendations.
Situation Assessment
Issue Tree Construction (MECE)
Hypothesis Formation
Quantitative Analysis
Qualitative Assessment
Framework Application
Recommendation Development
Executive Communication
Should we enter Market X?
├─ Market Attractiveness (IS the opportunity good?)
│ ├─ Market size and growth
│ ├─ Competitive intensity
│ └─ Profitability potential
│
├─ Strategic Fit (SHOULD we pursue it?)
│ ├─ Alignment with company strategy
│ ├─ Synergies with existing business
│ └─ Risk profile compatibility
│
└─ Ability to Win (CAN we succeed?)
├─ Competitive advantage
├─ Required capabilities vs current state
└─ Resource availability and commitment
Total Score = (Customer Value + Microsoft Value + Ecosystem Impact +
Technical Innovation + Engineering Efficiency +
Time to Production) / 6
Interpretation:
4.5-5.0: Strategic priority - immediate investment
3.5-4.4: Strong candidate - detailed planning
2.5-3.4: Conditional - requires optimization
1.5-2.4: Deferred - not currently strategic
<1.5: Decline - does not meet minimum criteria
# Strategic Recommendation: [Clear Decision Title]
## Recommendation
[One sentence: What should we do?]
## Three Key Messages
1. **[First key message]** - [Why it matters]
2. **[Second key message]** - [Supporting evidence]
3. **[Third key message]** - [What it means]
## Strategic Rationale
[2-3 paragraphs explaining the "why" behind the recommendation]
## Expected Impact
- Financial: [Revenue/cost impact with timeframe]
- Strategic: [Competitive advantage, market position]
- Organizational: [Capability building, culture]
## Implementation Roadmap
- **Phase 1 (Months 1-3)**: [Quick wins, foundations]
- **Phase 2 (Months 4-6)**: [Scale, optimization]
- **Phase 3 (Months 7-12)**: [Full deployment, measurement]
## Key Risks & Mitigation
1. **[Risk]** - Mitigation: [Strategy]
2. **[Risk]** - Mitigation: [Strategy]
## Investment Required
- Capital: $[amount]
- People: [FTE count] over [timeframe]
- Timeline: [Duration]
- Expected ROI: [X]% by [timeframe]
## Success Metrics
- [KPI 1]: [Target by date]
- [KPI 2]: [Target by date]
- [KPI 3]: [Target by date]
## Next Steps
1. **[Action]** - Owner: [Name], Due: [Date]
2. **[Action]** - Owner: [Name], Due: [Date]
Input: Should we invest in building an AI-powered customer service platform?
Workflow Execution:
1. Situation: Current support costs $5M/year, 24-hour response time,
customer satisfaction 3.2/5
2. Issue Tree (MECE):
├─ Market Opportunity
│ ├─ Cost savings potential
│ ├─ Customer experience improvement
│ └─ Competitive differentiation
├─ Technical Feasibility
│ ├─ AI/ML capabilities required
│ ├─ Data availability and quality
│ └─ Integration complexity
└─ Business Case
├─ Development cost and timeline
├─ ROI and payback period
└─ Risk vs reward profile
3. Hypothesis: "AI platform will reduce support costs by 60% while
improving satisfaction to 4.5/5 within 18 months"
4. Quantitative Analysis:
- Current cost: $5M/year
- Projected savings: $3M/year (60% reduction)
- Development cost: $2M
- Payback period: 8 months
- 5-year NPV: $12M
5. ISE Framework Scoring:
- Customer Value: 5/5 (CxO-validated cost savings + satisfaction)
- Company Value: 4/5 ($3M annual recurring savings)
- Ecosystem Impact: 3/5 (replicable across industry)
- Technical Innovation: 4/5 (frontier AI/ML)
- Engineering Effort: 4/5 (120 dev days)
- Time to Production: 4/5 (3 months MVP)
Composite Score: 4.0/5 - STRONG STRATEGIC PRIORITY
6. Framework: Porter's Five Forces shows AI as key competitive moat
7. Recommendation: "Invest $2M to build AI customer service platform"
8. Executive Summary: Three key messages format with roadmap
Output:
✅ RECOMMEND: Proceed with AI platform development
Expected Impact: $3M annual savings, 4.5/5 customer satisfaction
ROI: 150% over 5 years, 8-month payback
Next Step: Approve $2M budget, kickoff with 6-person team by Q2
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.