wm-atlas-anchor-chains

Generate Wardley Maps for each anchor with transitive dependency closures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you understand the specific dependencies and components that each user class relies on, revealing unique and shared infrastructure from their perspective.

Core Features & Use Cases

  • Per-Anchor Dependency Maps: Generates individual Wardley Maps for each anchor (user class), illustrating their direct and indirect dependencies.
  • Dependency Closure Analysis: Identifies components unique to an anchor versus those shared across multiple anchors.
  • Use Case: For a SaaS product, this Skill can show how different user personas (e.g., administrators, end-users, developers) interact with and depend on various parts of the system, highlighting areas for targeted improvement or potential coordination issues.

Quick Start

Generate per-anchor dependency maps for the project located at clients/example-org/projects/example-project.

Frequently Asked Questions about wm-atlas-anchor-chains

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

FAQPage Schema
How do I visualize per-anchor dependency chains for different user classes?

Dependency chain mapping using Wardley Maps decomposes complex value chains from individual user class perspectives, revealing unique versus shared transitive dependencies to clarify targeted strategic improvement areas.

What is the best way to analyze unique versus shared components across multiple user personas?

Dependency closure analysis identifies components unique to an anchor versus those shared across multiple anchors, mapping transitive dependencies from individual user class perspectives to reveal coordination issues in complex systems.

Do I need Node.js and npx to render Wardley Maps for supply chain strategic planning?

Yes, you need npx for OWM rendering to generate Wardley Maps. You also need access to previously generated strategy, needs, supply chain, evolution, and play artifacts for complete dependency mapping.

Can I use this for strategic analysis of complex SaaS systems with multiple user types?

Yes, this Skill applies to strategic analysis of complex systems by decomposing value chains from individual user class perspectives, making it suitable for SaaS environments with distinct personas like administrators and developers.

What prerequisites are required before generating per-anchor dependency maps?

Prerequisites include Node.js for npx OWM rendering and access to previously generated strategy, needs, supply chain, evolution, and play artifacts to successfully generate per-anchor dependency maps.

Why does dependency mapping require access to previously generated strategy and evolution artifacts?

Access to previously generated strategy, needs, supply chain, evolution, and play artifacts is required because they provide the foundational context needed to accurately decompose value chains and map transitive dependencies.