sb

Runs consistency checks over an imported service blueprint and records what they find as triageable findings — gaps a scenario never covers, jargon customers would not say, channel conflicts, KPI drift, ownership mismatches, value dead-ends, invisible fees. Use when the user asks to "audit the blueprint", "check Map your service for gaps/inconsistencies", "what's wrong with this scenario", "re-run the checks", "sanity check my blueprint", "health check", "is my blueprint consistent", or wants a finding dismissed or resolved ("that jargon one is fine, dismiss it"). Requires an imported blueprint — for building or importing one, use the sb:map skill; for hypothetical changes, use sb:whatif.

Creates, imports, translates, presents, and evolves service blueprints end-to-end. Use whenever the user mentions a service blueprint, journey map, customer journey, user journey documentation, service design, frontstage/backstage, swimlane service diagram, Shostack blueprint, or asks to "map how our service works", "map how customers actually experience X", document a service process, compare a designed process against reality, import a FigJam/Figma/Miro/spreadsheet blueprint into an app or database (e.g. "get our FigJam service map into Supabase"), turn service docs or discovery research into a blueprint, or update/redeploy an existing blueprint workspace. Also use when a directory contains blueprint-workspace.json or a blueprint/ IR directory. For checking an already-imported blueprint for inconsistencies use sb:audit; for tracing a hypothetical change before committing to it use sb:whatif.

Cuts a stakeholder-ready view out of an existing service blueprint — one actor's journey, one moment across every lane, one lane end to end, or one cell read closely — and writes it back as a slice the app can present. Use when the user asks to "pull out the customer's journey", "show what everyone is doing at check-in", "make a storyboard from the blueprint", "what does the support team own", "turn this blueprint into something I can show the client/exec/team", or mentions a slice, journey summary, lane spec, cell brief, or storyboard of a blueprint that already exists. Requires an imported, signed-off blueprint — for creating or importing the blueprint itself, use the sb:map skill instead.

Traces the consequences of a hypothetical change to an existing service blueprint before anyone commits to it — replays a scenario as if the change were made, restages a moment across the visibility line (frontstage/backstage), or prioritizes which cells matter most right now. Use when the user asks "what if we removed/automated/moved X", "what breaks if…", "what's the impact of…", "should this be customer-visible", "which cells should we focus on", or wants an accepted analysis promoted into an actual blueprint change. Requires an imported blueprint — for building one use sb:map; for finding present-tense inconsistencies use sb:audit.