What problem does it solve? Product problems that look like UX issues are often structural: brittle handoffs between teams, undocumented dependencies, and failure modes nobody modeled. This Skill makes the invisible machinery behind a product experience visible so teams can diagnose root causes and redesign the system, not just the symptom. ## 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 single points of failure across teams and systems. - Failure Mode & State Analysis: Models system states, cascade effects, recovery paths, and graceful degradation tiers, and flags architectures that structurally enable dark patterns. - Use Case: Ask "What breaks when our payment provider goes down?" and receive a dependency map with blast-radius analysis, recovery paths, and a visual service blueprint. ## Quick Start Ask the assistant to map out the service blueprint and dependencies behind your checkout flow, including what breaks when a key service fails.
