From wardley-mapping
Analyzes strategic positions using Wardley Mapping to recommend competitive, evolution, doctrine, or comprehensive plays for tech decisions like buy vs build authentication or container orchestration strategy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wardley-mapping:strategic-analysisThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze strategic position and recommend plays based on Wardley Mapping principles.
Analyze strategic position and recommend plays based on Wardley Mapping principles.
Based on perspective:
Use MCP servers to gather intelligence:
strategy-mapmaker agent for mappingstrategic-plays skill for play identificationevolution-analysis skilldoctrine-advisor agentExecute all three perspectives and synthesize findings.
Combine findings into:
Present comprehensive strategic analysis with prioritized recommendations.
/strategic-analysis "buy vs build for authentication"
Analyzes the strategic implications of building vs. buying authentication capability.
/strategic-analysis "market entry strategy" perspective="competitive"
Focuses on competitive positioning for market entry.
/strategic-analysis "container orchestration strategy" perspective="evolution"
Analyzes the evolution of container orchestration options.
/strategic-analysis "digital transformation readiness" perspective="doctrine"
Assesses organizational doctrine for digital transformation.
# Strategic Analysis: [Context]
## Executive Summary
[Key findings and top recommendations in 3-5 bullets]
## Situation Assessment
### Current Position
[Where you are now on the map]
### Competitive Landscape
[Who else is here and where are they positioned]
### Evolution State
[What's evolving and how fast]
## Analysis by Perspective
### Competitive Analysis
[Positioning, threats, opportunities]
### Evolution Analysis
[Movement patterns, timing considerations]
### Doctrine Assessment
[Organizational capability and gaps]
## Strategic Options
| Option | Pros | Cons | Risk | Fit |
|--------|------|------|------|-----|
| [Option 1] | [Benefits] | [Drawbacks] | [Risk level] | [How well it fits] |
## Recommended Strategy
### Primary Recommendation
[What to do and why]
### Supporting Actions
1. [Action 1]
2. [Action 2]
3. [Action 3]
### Timeline
- Immediate: [Actions]
- Short-term (1-3 months): [Actions]
- Medium-term (3-6 months): [Actions]
## Risk Analysis
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk] | High/Med/Low | High/Med/Low | [How to address] |
## Success Criteria
| Metric | Current | Target | Timeframe |
|--------|---------|--------|-----------|
| [Metric] | [Now] | [Goal] | [When] |
## Next Steps
1. [Immediate next step]
2. [Following step]
3. [Validation step]
## Assumptions and Limitations
- [What was assumed]
- [What couldn't be analyzed]
Depending on context, the analysis may incorporate:
/wardley-map: Create a Wardley Map first/doctrine-assessment: Deep doctrine assessmentstrategic-plays: Strategic gameplay patternsevolution-analysis: Component evolution assessmentdoctrine-assessment: Organizational doctrine evaluationnpx claudepluginhub melodic-software/claude-code-plugins --plugin wardley-mappingVisualizes value chains, evolution stages, landscapes, and gameplay patterns via Wardley Mapping for tech strategy, competitive analysis, and architecture decisions.
Identifies strategic options and gameplay patterns from Wardley Maps for competitive advantage. Useful for planning, design guidance, and best practices.
Creates or updates Wardley Maps of value chains, plotting user needs, components, evolution stages (genesis, custom, product, commodity), movements, patterns, and strategic gameplay. Outputs YAML landscape and decision log entries.