blueprint

Maps and redesigns service blueprints, ecosystem dependencies, and process architecture behind product experiences.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/ishfuseini/usecase-gen --skill blueprint-ishfuseini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/ishfuseini/usecase-gen/tree/main/agent/skills/blueprint
Command: npx skills add https://github.com/ishfuseini/usecase-gen --skill blueprint-ishfuseini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product problems that look like UX issues are often systems problems: brittle handoffs, undocumented dependencies, and unclear ownership hide behind every touchpoint. 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, support infrastructure, and lines of interaction and visibility, with optional HTML, Figma, or pencil.dev diagram output. - Dependency & Ecosystem Mapping: Documents actors, data flows, ownership boundaries, and structural risks such as single points of failure. - Failure Mode & Scalability Analysis: Models system states, cascade effects, recovery paths, and scaling thresholds across markets and segments. - Use Case: A team asks why onboarding is slow. The Skill produces a service blueprint revealing that three teams own different steps with a 48-hour manual review, then proposes a redesigned process architecture with clear handoffs. ## Quick Start Ask the assistant to map out the systems and dependencies behind your service and create a service blueprint for it.

Frequently Asked Questions about blueprint

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

FAQPage Schema
How do I create a service blueprint for a product experience?

Invoke the blueprint skill and describe the service you want mapped. It produces frontstage, backstage, and support-process lanes with lines of interaction and visibility, and can render the blueprint as a self-contained HTML diagram, a Figma file, or a pencil.dev document.

What is the difference between a service blueprint and a user journey map?

A service blueprint maps the organizational machinery behind an experience: backstage processes, support systems, dependencies, and ownership. A journey map covers what the user sees and does. This skill handles the systems side and hands off screen-level flows to the journey skill.

Can the blueprint diagram be exported to Figma or HTML?

Yes. The skill asks which format you want before producing the deliverable. HTML is the default self-contained option, while Figma output uses the Figma MCP integration and pencil.dev output uses the pencil MCP integration.

When should I use systems mapping instead of UX design?

Use systems mapping when the question is how the service works structurally: dependencies, handoffs, failure modes, scaling limits, or ownership. If the work shifts to designing specific screens or interactions, that belongs to journey-level design instead.

Does the blueprint skill analyze failure modes and scaling limits?

Yes. It models system states, transition triggers, failure modes with blast radius, recovery paths, and graceful degradation tiers. It also identifies scaling thresholds and migration paths for new markets, segments, or product lines.