wm-atlas-inertia

Generate inertia-focused Wardley Maps and analyze component dependencies and evolve arrows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and visualizes organizational inertia, highlighting components that resist change and the strategic tension this creates.

Core Features & Use Cases

  • Inertia Identification: Pinpoints components marked with 'inertia' on a Wardley Map.
  • Dependency Mapping: Shows components affected by inertia (dependents) and those contributing to it (dependencies).
  • Tension Analysis: Highlights conflicts between strategic intent (evolve arrows) and organizational resistance.
  • Use Case: Understand why a critical strategic initiative is stalled by visualizing the specific contractual, cultural, or technical barriers preventing key components from evolving.

Quick Start

Generate an inertia-focused Wardley Map for the current project using the wm-atlas-inertia skill.

Frequently Asked Questions about wm-atlas-inertia

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

FAQPage Schema
How do I map organizational inertia and resistance to change using Wardley Mapping?

You can visualize organizational inertia by generating a Wardley Map that identifies components marked with inertia, their dependents, and the evolve arrows acting upon them. This highlights the contractual, cultural, or technical barriers preventing strategic evolution.

Why does a strategic initiative stall when components resist evolving?

Strategic initiatives stall due to organizational inertia, which creates tension between strategic intent (evolve arrows) and the components resisting change. Analyzing this resistance reveals the specific dependencies and barriers blocking organizational evolution.

Do I need Node.js to render an inertia-focused Wardley Map?

Yes, you need Node.js to render an inertia-focused Wardley Map via the OWM rendering tool cli-owm. This environment allows the Skill to generate the visual map and supplement the organizational change analysis with research.

How can I analyze the causes of organizational resistance from a Wardley Map?

You can analyze organizational resistance causes by evaluating evolution assessments, strategy plays, and decision logs associated with the inertia-marked components. This dependency analysis identifies why specific components resist organizational change.

Can dependency analysis show which components are affected by organizational inertia?

Yes, dependency analysis identifies components affected by inertia (dependents) and those contributing to it (dependencies). This mapping clarifies the contractual, cultural, or technical barriers creating strategic tension within the organizational structure.

What is the best way to visualize strategic tension between intent and organizational resistance?

The best way to visualize strategic tension is by generating an inertia-focused Wardley Map that highlights conflicts between strategic intent (evolve arrows) and organizational resistance. This reveals the specific barriers preventing key components from evolving.