What problem does it solve? Technology decisions fail when a bespoke capability is treated as a finished product or a commodity is custom-integrated. This Skill places each named technology, capability, or vendor category on Simon Wardley's evolution axis — Genesis, Custom built, Product (+rental), or Commodity (+utility) — anchored in observable evidence, so build-vs-buy decisions and delivery methods match the component's actual maturity. ## Core Features & Use Cases - Evidence-anchored stage placement: Assigns one of the four Wardley stages using eight observable placement questions covering supplier count, switching cost, pricing model, and integration time. - Way-of-working translation: States the delivery method each stage implies — agile experiments, lean builds, playbook adoption, or utility purchase — and flags mismatches with the surrounding recommendation. - Cross-stage comparison guardrails: Forces explicit acknowledgment when compared components sit at different stages before any feature-by-feature comparison. - Use Case: A vendor sells a "product" that needs four months of per-customer tuning. The Skill tags it as Custom built, cites the integration time as evidence, and recommends lean delivery borrowed from the closest comparable build instead of a two-week product adoption plan. ## Quick Start Use the evolution-stage skill to tag each technology in my comparison with its Wardley evolution stage, an evidence-based rationale, and the way of working each stage implies.
