What problem does it solve? Product problems that look like UX issues are often structural systems problems: brittle handoffs between teams, undocumented dependencies, and failure modes nobody mapped. This Skill makes the invisible machinery behind a product experience visible so teams can diagnose root causes and redesign how services actually work. ## Core Features & Use Cases - Service Blueprinting: Maps frontstage touchpoints, backstage processes, and support infrastructure with lines of interaction and visibility, exportable as self-contained HTML, Figma, or pencil.dev diagrams. - Dependency & Ecosystem Mapping: Documents actors, data flows, ownership boundaries, and structural risks such as single points of failure. - Failure Mode & State Analysis: Models system states, cascade effects, recovery paths, and graceful degradation tiers, and flags architectures that enable dark patterns. - Use Case: Ask why a checkout flow keeps failing and receive an end-to-end blueprint showing which backend services, team handoffs, and third-party dependencies break under load, plus a migration path. ## Quick Start Ask the assistant to map out the systems and dependencies behind your checkout service as a service blueprint with an HTML diagram.
