wm-atlas-layers

Generate depth-separated Wardley Maps by component visibility layers.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/monkeypants/consultamatron --skill wm-atlas-layers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wm-atlas-layers
Source: https://github.com/monkeypants/consultamatron/tree/main/commons/wardley_mapping/skills/wm-atlas-layers
Command: npx skills add https://github.com/monkeypants/consultamatron --skill wm-atlas-layers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps in understanding the strategic landscape by breaking down a Wardley Map into distinct layers based on component visibility, revealing how the nature of the organization's landscape changes from user-facing elements to infrastructure.

Core Features & Use Cases

  • Depth-Separated Maps: Generates three distinct maps: User-visible, Capabilities, and Infrastructure.
  • Layer Analysis: Provides insights into the evolution maturity, complexity, and cost characteristics of each layer.
  • Interface Identification: Highlights the dependencies and interfaces between different layers.
  • Use Case: After creating a comprehensive Wardley Map, use this Skill to analyze how user needs are supported by capabilities, which in turn rely on infrastructure, and identify potential bottlenecks or areas for strategic focus.

Quick Start

Use the wm-atlas-layers skill to generate depth-separated maps for the project located at clients/example-org/projects/example-project.

Frequently Asked Questions about wm-atlas-layers

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

FAQPage Schema
How do I visualize Wardley Maps by component visibility layers?

Depth-separated Wardley Maps are generated by breaking down a comprehensive map into user-visible, capabilities, and infrastructure layers. This reveals how the organization's landscape changes from user-facing elements to infrastructure.

How do I analyze evolution maturity and cost across different strategy layers?

Analyze evolution maturity and cost across strategy layers by examining depth-separated maps. The Skill assesses the complexity and cost characteristics of each visibility layer and identifies cross-layer interfaces and dependencies.

Do I need Node.js to render Online Wardley Maps for strategy visualization?

Yes, Node.js is required to render Online Wardley Maps. The Skill uses npx to execute the cli-owm rendering tool and requires an agreed OWM map from the strategy stage as input.

What is the best way to identify cross-layer interfaces in a Wardley Map?

The best way to identify cross-layer interfaces in a Wardley Map is by generating depth-separated maps. This highlights the dependencies and interfaces between user-visible, capability, and infrastructure layers.

Can I use an existing Wardley Map to analyze infrastructure bottlenecks?

Yes, you can use an agreed OWM map from the strategy stage to analyze infrastructure bottlenecks. The Skill isolates the infrastructure layer to evaluate evolution maturity and identify potential strategic focus areas.