Automated summary
Produces a Wardley Map by identifying the user need, the value chain, and each component's position along the evolution axis, then derives build-vs-buy recommendations.
Strengths
- Organizes output into actionable sections: value chain, evolution assessment, ASCII map, and movement analysis
- Explicitly links map position to a concrete decision (build on the left, buy on the right)
- Covers inertia points and commoditization threats, which strategic analyses often skip
- Gives clear indicators for distinguishing Genesis, Custom, Product, and Commodity stages
Limitations
- The map itself is a static ASCII diagram with no interactive visualization or export
- Output quality depends heavily on the context the user supplies about their market and components
- Analysis stays qualitative: no cost, timeline, or market-share estimates
Use it to frame a technology strategy, investment, or build-vs-buy decision for an existing product.
Avoid it when you need a detailed execution plan, budget figures, or process mapping without an evolution dimension.
Security analysis
SafeThe skill is a purely instructional strategic-analysis template. It declares no tools, contains no executable commands, network calls, secrets handling, or destructive actions, and only asks the agent to produce a structured Wardley Map.
No concerns found
How this analysis is madeExamples
Run a Wardley map for our analytics platform. Users are internal data analysts who need self-serve dashboards. We currently build our own query engine and storage layer in-house — help me decide what to keep building and what to buy.Map the value chain for our B2B SaaS onboarding product and tell me which components are sliding toward commodity, where we have inertia, and what our real differentiators are.We're deciding where to invest next quarter. Build a Wardley map starting from the user need 'small teams track project progress', position each component on the evolution axis, and recommend short-term actions plus what to stop building.name: wardley description: Wardley Mapping strategic analysis—map value chains against evolution to reveal build vs buy decisions and competitive dynamics. Use for technology strategy or investment decisions. user-invocable: true
Wardley Map
Create a strategic map showing components positioned by their evolution stage and visibility in the value chain.
Instructions
Identify the user need, map the value chain of components required to meet it, and position each component on the evolution axis.
Output Format
Context: [What situation we're mapping] User: [Who the user is] User Need: [What they're trying to accomplish]
Value Chain Identification
Working backward from user need:
| Component | Depends On | Visibility | |-----------|------------|------------| | [User Need] | [what it requires] | High (User-facing) | | [Component A] | [what it requires] | High/Med/Low | | [Component B] | [what it requires] | High/Med/Low | | [Infrastructure] | [base requirements] | Low (Hidden) |
Evolution Assessment
| Component | Evolution Stage | Evidence | |-----------|-----------------|----------| | [Component A] | Genesis / Custom / Product / Commodity | [Why at this stage] | | [Component B] | Genesis / Custom / Product / Commodity | [Why at this stage] |
Evolution Indicators:
- Genesis: Novel, poorly understood, no standard, high uncertainty
- Custom: Emerging practices, divergent approaches, experimentation
- Product: Feature differentiation, rental/purchase models, scalable
- Commodity: Standardized, utility pricing, essential but undifferentiated
The Map
VISIBLE │
TO │ [User Need]
USER │ │
│ ▼
│ [Component A]
│ │
│ ▼
INVISIBLE│ [Component B]
│
└──────┬──────┬──────┬──────┬──────►
GENESIS CUSTOM PRODUCT COMMODITY
I II III IV
Movement Analysis
What's evolving rightward? | Component | Current Stage | Evolving Toward | |-----------|---------------|-----------------| | [component] | [stage] | [next stage] |
Inertia Points
- [Component with inertia] — [why we might resist]
Strategic Analysis
Build vs. Buy
| Component | Recommendation | Rationale | |-----------|----------------|-----------| | [Genesis/Custom] | Build | Differentiator | | [Commodity] | Buy | Commodity, not differentiating |
Competitive Dynamics
Our differentiators (left side of map):
- [Component we do differently]
Commoditization threats:
- [Component becoming commodity]
Recommendations
Short-term actions:
- [Action based on map insights]
What to stop doing:
- [Component to outsource/buy instead of build]
Key Insight:
[Main strategic takeaway from the mapping exercise]
Guidelines
- Always start with user need
- Everything evolves left to right (genesis → commodity)
- Build on the left (differentiation), buy on the right (commodity)
- Watch for inertia—past success creates resistance to change
$ARGUMENTS
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/wardley-mapping-strategic-analysis-ms47vpco/download' --output '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md.part' && mv '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md.part' '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md' && test -s '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/wardley' && cp -R '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco' '.claude/skills/wardley'Cursor
test -f '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md' && test -s '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/wardley' && cp -R '.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco' '.cursor/skills/wardley'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/wardley-mapping-strategic-analysis-ms47vpco'openskills read 'wardley-mapping-strategic-analysis-ms47vpco'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/wardley-mapping-strategic-analysis-ms47vpco/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.