eterdis-wardley-map

Create Wardley Maps visualizing value chains and component evolution.

6|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/eterdis/strategy-skills --skill eterdis-wardley-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eterdis-wardley-map
Source: https://github.com/eterdis/strategy-skills/tree/main/wardley-map
Command: npx skills add https://github.com/eterdis/strategy-skills --skill eterdis-wardley-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wardley Mapping addresses strategic ambiguity by visualizing the value chain and how components move along the evolution axis, enabling teams to decide where to invest, what to commoditize, and how to respond to market shifts.

Core Features & Use Cases

  • End-to-end mapping from user need through value chain to evolution stages, with a clear movement narrative.
  • Supports three modes: Diagnostic (build from scratch), Review (update positions), and Alert Triggers (set tripwires for future reassessments).
  • Produces a shared company-context.md with map, key plays, inertia points, and alert definitions for ongoing governance.

Quick Start

Begin a Wardley-mapping session by loading your company-context.md and drafting an initial value-chain map with the user need at the top.

Frequently Asked Questions about eterdis-wardley-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a Wardley Map and how does it visualize a value chain?

A Wardley Map visualizes the value chain from user need through components to evolution stages, placing each element from Genesis to Commodity. It clarifies strategic ambiguity by showing component movement and enabling teams to decide where to invest or commoditize.

How do I create a Wardley Map for strategic planning?

To create a Wardley Map, load a company-context.md file and draft the initial value chain with the user need at the top. Position each component from Genesis to Commodity, add movement notes, and define alert triggers for future reassessments.

Do I need a company-context file to map component evolution?

Yes, the mapping process relies on a company-context.md file to establish the baseline. It defines component ownership, initial positions on the evolution axis, and alert triggers for ongoing strategic governance and reassessment.

Can I update existing value chain positions during a strategy review?

Yes, the mapping process supports a Review mode specifically for updating component positions on the evolution axis. It enables teams to identify moving components, adjust strategic plays, and reassess inertia points when market shifts occur.

How do alert triggers work in Wardley Mapping?

Alert triggers act as strategic tripwires for future reassessment of the value chain. They monitor moving components along the evolution axis, prompting updates to the company-context.md and re-evaluating plays when market shifts happen.

What distinguishes diagnostic mapping from alert-driven reassessments?

Diagnostic mapping builds the value chain from scratch to establish baseline evolution stages. Alert-driven reassessments respond to triggered tripwires, updating component positions and strategic plays within the existing company-context.md for ongoing governance.