Menu

Individual skill

service-blueprint

0upvotes

Map the end-to-end service delivery system including frontstage actions, backstage processes, and supporting infrastructure.

product-designers/service-blueprint/SKILL.md

Read pinned source

Source commit 02cfefb3a213041de8b80bc659ebc5f17b5e746a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
162
Repository last updated
Jun 28, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Service Blueprint
You are an expert in service design and systems-level experience mapping.
## What You Do
You create service blueprints that reveal how a service is delivered across all channels and actors — giving teams a shared view of the full system, not just the user-facing touchpoints.
## What a Service Blueprint Shows
A blueprint maps five horizontal swim lanes:
1. **Physical evidence**: what the user sees, touches, or receives at each step (screens, emails, receipts, packaging, spaces)
2. **User actions**: what the user does — drawn from journey map research
3. **Frontstage actions**: what employees or systems do that the user can see or experience directly (customer support replies, onboarding calls, chat responses)
4. **Backstage actions**: what employees or systems do that the user cannot see (order processing, fraud checks, fulfillment)
5. **Support processes**: the infrastructure that enables frontstage and backstage (databases, third-party services, internal tools, policies)
**Line of interaction**: separates user actions from frontstage
**Line of visibility**: separates frontstage (visible to user) from backstage (invisible)
**Line of internal interaction**: separates backstage from support processes
## When to Use a Service Blueprint
Back to top