---
name: skill-service-blueprint
type: skill
description: >-
  Build a service blueprint — lay a stage spine across the evidence, customer,
  frontstage, backstage, and support lanes, connect the actor's traversal to the
  service stack behind it, colour-code confidence, and flag the conversion gaps.
  Use this whenever Sonar needs to connect the front-stage experience to what
  delivers it, or to expose where the service breaks down behind a leak. Reads
  convention-user-modelling; produced in Figma/FigJam, so execution routes to
  agent:claude. Surfaced by the a1.Muse engagement.
---

# service-blueprint

Sonar's depth skill. A journey map shows the experience from the user's side; a blueprint adds everything behind the curtain that delivers it, so a front-stage leak can be traced to the backstage cause.

## Trigger

A journey or diagnostic has shown *where* the experience breaks; the blueprint shows *why*, by connecting each front-stage moment to the people, process, and systems behind it. Run it after the stage spine and the user model are settled.

## Behaviour

1. **Take the stage spine.** Reuse the stages from the journey map or conversion diagnostic, so the blueprint and the diagnostic line up column for column.
2. **Lay the lanes.** For each stage, fill the five lanes top to bottom:
   * **Evidence** — what the user sees or receives at this stage.
   * **Customer** — what the user does, thinks, feels (the line of interaction sits below this).
   * **Frontstage** — the service actions the user is aware of (the line of visibility sits below this).
   * **Backstage** — the service actions the user does not see.
   * **Support** — the systems, tools, and partners that enable the stage.
3. **Connect the traversal and the stack.** Draw the actor's path across the lanes and the dependencies down the stack, so a moment of truth and the chain that delivers it are visible together.
4. **Colour-code confidence.** Mark each element known / assumed / gap, so the picture shows where the service is understood and where it is inferred.
5. **Flag conversion gaps.** Where a blueprint element sits under a leak from the diagnostic, flag it — the blueprint is where a conversion leak meets its operational cause.

## Notation

A shared visual convention keeps blueprints legible across engagements:

* **Squares** — blueprint elements (the content of a lane at a stage).
* **Post-its, yellow** — notes and observations.
* **Post-its, red** — open questions and unknowns.
* **Colour fill** — confidence: known, assumed, or gap.

## Reads

`convention-user-modelling` (modes and scenarios feed the customer lane; the journey map feeds the spine), the conversion diagnostic's leaks where one exists.

## Surface

Produced in Figma/FigJam. Execution that needs the Figma MCP routes to `agent:claude` (per `convention-linear`); Sonar specifies, the visual is built on that surface.

## Guardrails

Reuse the diagnostic's stage spine — don't invent a parallel one. Colour-code confidence honestly; an assumed element shown as known hides risk. Flag gaps rather than smoothing them over. The blueprint diagnoses and specifies; it does not design the fix. Propose-only.