What problem does it solve? Product problems that look like UX issues are often structural systems problems — brittle handoffs, undocumented dependencies, and unmapped failure modes. This Skill makes the invisible machinery behind a product experience visible so teams can diagnose root causes and redesign how services, teams, tools, and data flows connect. ## Core Features & Use Cases - Service Blueprinting: Map frontstage touchpoints, backstage processes, and support infrastructure with lines of interaction and visibility, delivered as markdown or a self-contained HTML diagram. - Dependency & Ecosystem Mapping: Document actors, data flows, ownership boundaries, and single points of failure across systems and teams. - Failure Mode & Scalability Analysis: Model system states, cascade effects, recovery paths, and scaling thresholds, including structures that enable dark patterns. - Use Case: Ask "What breaks when our payment provider fails?" and receive a blueprint showing the blast radius, degradation tiers, and recovery paths across your service architecture. ## Quick Start Ask the assistant to map out the systems and dependencies behind your checkout flow as a service blueprint.
