blueprint

Map and analyze end-to-end systems to produce service blueprints and process diagrams.

116|9|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ghaida/intent --skill blueprint-ghaida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/ghaida/intent/tree/main/skills/blueprint
Command: npx skills add https://github.com/ghaida/intent --skill blueprint-ghaida

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map and analyze the end-to-end systems behind a product experience to reveal how services, teams, processes, and data flows interact, enabling structural improvements rather than surface fixes.

Core Features & Use Cases

  • Service blueprinting: End-to-end maps showing frontstage, backstage, support processes, data flows, and ownership boundaries.
  • Ecosystem & dependency mapping: Identify actors, touchpoints, data flows, dependencies, and ownership.
  • Process architecture: Design decisions, handoffs, timing, exception handling, and operational feasibility.
  • System state & failure mode analysis: Model system states, transitions, failure modes, recovery paths, and graceful degradation.
  • Scalability & evolution planning: Plan for growth, multi-context applicability, migrations, governance.
  • Decision documentation: Capture decisions, rationale, open questions, assumptions, and dependencies.
  • Output artifacts: Create service blueprints, ecosystem maps, process diagrams, and data-flow models.

Quick Start

Map the service blueprint for your current checkout flow to start identifying bottlenecks and dependencies.

Frequently Asked Questions about blueprint

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

FAQPage Schema
What is a service blueprint and how does it map product ecosystems?

A service blueprint maps end-to-end product ecosystems by revealing how services, teams, data flows, and processes interact. It produces structural documentation like ecosystem maps and process diagrams to enable system-level improvements rather than surface fixes.

How do I create a service blueprint for an existing checkout flow?

To create a service blueprint for a checkout flow, map the frontstage, backstage, and support processes while identifying data dependencies and ownership boundaries. This structural documentation reveals bottlenecks and operational design flaws across cross-functional workflows.

Can I use process architecture to analyze failure modes and system states?

Yes, process architecture analysis models system states, transitions, and failure modes. It generates state and failure models that document recovery paths and graceful degradation strategies for complex operational designs.

When do I need ecosystem mapping for cross-functional workflows?

You need ecosystem mapping when scaling products across cross-functional workflows to identify actors, touchpoints, data flows, and dependencies. It captures ownership boundaries and generates scalability plans for multi-context applicability and migrations.

What's the best way to document operational design decisions and dependencies?

The best way to document operational design decisions is by capturing decisions, rationale, open questions, and assumptions alongside dependency analysis. This produces decision records that align process architecture with ecosystem governance.