wm-atlas-doctrine

Evaluate Wardley maps against doctrine principles and generate analysis documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps ensure that strategic decisions align with established Wardley doctrine principles, identifying potential misalignments in sourcing, inertia management, and focus.

Core Features & Use Cases

  • Doctrine Principle Assessment: Evaluates a Wardley map strategy against seven key doctrine principles.
  • Sourcing Alignment: Checks if component sourcing (build/buy/outsource) matches their evolution stage.
  • Inertia Management: Assesses how the strategy addresses or ignores inertia.
  • Focus & Transparency: Analyzes the strategy's focus and how well it reveals assumptions.
  • Use Case: After developing a Wardley map for a new product strategy, use this Skill to get a critical review of whether the proposed sourcing for commodity components is too slow, or if inertia from legacy systems is being ignored.

Quick Start

Evaluate the strategy map located at strategy/map.agreed.owm against Wardley doctrine principles.

Frequently Asked Questions about wm-atlas-doctrine

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

FAQPage Schema
How do I evaluate a Wardley mapping strategy against doctrine principles?

You can assess a Wardley mapping strategy against doctrine principles by analyzing sourcing alignment, inertia management, and transparency, generating a prose-heavy assessment document with focused map excerpts.

What is Wardley doctrine assessment for strategic sourcing and inertia?

Wardley doctrine assessment evaluates whether component sourcing matches evolution stages and how effectively a strategy addresses legacy system inertia and focus constraints.

Do I need Node.js and npx to render OWM files for strategy analysis?

Yes, Node.js and npx are required to run cli-owm for rendering OWM files and generating map excerpts that highlight specific doctrine adherences or violations.

How do I check if my component sourcing aligns with its evolution stage in Wardley mapping?

To check component sourcing alignment, evaluate your Wardley map strategy to verify that build, buy, or outsource decisions appropriately match the evolution stage of each component.

Can I generate map excerpts highlighting specific Wardley doctrine violations?

Yes, you can generate optional focused map excerpts highlighting specific doctrine adherences or violations, providing visual context alongside the prose-heavy analysis document.

What are the limitations of using doctrine principles for Wardley map strategy review?

The review is limited to seven established doctrine principles like flow optimisation and common component usage, meaning it does not introduce new strategic frameworks but evaluates against existing Wardley doctrine.