morphological-analysis

Maps solution spaces with Zwicky box parameters and cross-consistency assessment to count internally consistent configurations.

4|1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/radarist/structured-analytic-skills --skill morphological-analysis-radarist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: morphological-analysis
Source: https://github.com/radarist/structured-analytic-skills/tree/main/skills/morphological-analysis
Command: npx skills add https://github.com/radarist/structured-analytic-skills --skill morphological-analysis-radarist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When a design, architecture, or business-model problem has many interacting choices, teams anchor on a few familiar combinations and miss viable ones. This Skill structures the problem as a morphological field (parameters × discrete values), prunes impossible value pairs through a reasoned Cross-Consistency Assessment, and reports exactly how many internally consistent configurations remain. ## Core Features & Use Cases - Zwicky box construction: Define 4–8 MECE parameters with 2–6 discrete values each and compute the raw configuration count as the product of value counts. - Cross-Consistency Assessment (CCA): Judge every cross-parameter value pair as consistent or excluded, with each exclusion typed logical, empirical, or normative and carrying a stated reason. - Deterministic companion tool: scripts/morph.py enumerates the consistent solution space, filters configurations by driver values, and audits CCA coverage — stdlib-only Python, offline, with JSON output. - Use Case: A product team exploring residential home-energy architectures defines five parameters (storage, control, revenue, ownership, pricing), records nine reasoned exclusions, and learns that 172 of 432 raw configurations are internally consistent — 54 of which can sell grid flexibility. ## Quick Start Ask the assistant to run a morphological analysis on your design problem, listing the parameters and their options so it can build the Zwicky box, assess pair consistency, and count the viable configurations.

Frequently Asked Questions about morphological-analysis

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

FAQPage Schema
How do I run a morphological analysis on a design problem?▼

Define 4-8 MECE parameters with 2-6 discrete values each, build the Zwicky box, then assess every cross-parameter value pair for consistency. The companion script morph.py computes raw and consistent configuration counts and lists solutions filtered by driver values.

What is a cross-consistency assessment in a Zwicky box?▼

Cross-consistency assessment judges every pair of values from different parameters as compatible or excluded, with no direction or causality. Each exclusion is typed logical, empirical, or normative and must carry a one-line reason a colleague could dispute.

When should I use morphological analysis instead of scenario planning?▼

Use morphological analysis when more than two dimensions interact and consistency between choices is the issue. Scenario planning fits two critical uncertainties narrated into four futures; morphological analysis enumerates and prunes a larger configuration space.

Does the morph.py script require external Python packages?▼

No, morph.py uses only the Python standard library and runs offline on Python 3.9 or later. It reads a JSON box description and supports box, space, solutions, and cca commands, each with a --json output flag.

What are the limitations of morphological analysis?▼

It cannot model directional or causal influences between factors — use cross-impact analysis for that. Fields beyond about eight parameters become unwieldy, and un-assessed value pairs must never be treated as consistent by default.