name: kai-business-blueprint description: Use when turning presales requirements, meeting notes, or solution materials into editable business capability blueprints, swimlane flows, and application architecture diagrams. Use when generating blueprint JSON, static HTML viewers, or exporting to SVG, draw.io, Excalidraw, or Mermaid formats. When no standard export template applies, default to free-flow output.

Business Blueprint Skill

Use the Python scripts in this repository as the execution surface.

Output Directory

All generated files (blueprint JSON, viewers, exports) go into projects/workspace/ — not the repository root.

python scripts/business_blueprint/cli.py --plan projects/workspace/solution.blueprint.json --from "..."
python scripts/business_blueprint/cli.py --project projects/workspace/solution.blueprint.json
python scripts/business_blueprint/cli.py --export projects/workspace/solution.blueprint.json

Industry Selection

Choose --industry from exactly one of: "common", "finance", "manufacturing", "retail". Select the closest match based on the user's domain and materials; do not invent other values.

How to Generate a Blueprint

The AI agent is responsible for entity extraction. The Python tool handles JSON writing, visualization, and export.

7w4.net小蔥技能站收錄全網優質技能，值得收藏。

Step 1: Read industry hints

Read the seed template at business_blueprint/templates/{industry}/seed.json and get the industryHints.checklist.

Step 2: Extract entities from source text

Using the user's source material AND the industry hints checklist, extract: - capabilities: business capability areas (name, description) - actors: roles/people involved (name) - flowSteps: business process steps (name, actorId, capabilityIds, stepType) - systems: IT systems that support capabilities - See references/entities-schema.md for all entity field definitions - See references/systems-schema.md for systems category/layer rules - See scripts/business_blueprint/templates/common/seed.json for field examples

Domain-knowledge mode (when seed has meta.blueprintType: "domain-knowledge", e.g. cross-border-ecommerce): entities go into library.knowledge.* (painPoints / strategies / rules / metrics / practices / pitfalls), not the architecture buckets above. The seed's industryHints.knowledgeHints.namingHints section, when present, dictates content granularity: - strategy.name must be a 4-10 字 product-grade noun phrase (e.g. "統一歸因模型", "AIGC 素材工廠"), not an action ("最佳化素材") or a dimension ("測款節奏"). Reference the seed's strategy_named_examples. - painPoint.audience and strategy.audience are free-string fields tagging the primary persona ("品牌方/DTC", "平臺賣家", "代運營/服務商"). Multiple values comma-separated. No standalone persona entity is required. - metric.forecast: {direction, magnitude, unit} is optional and used for commitments to the customer ("ROAS 提升 25%"). Keep value/benchmarkContext for current baseline; the two coexist as "now X, can reach Y".

These fields are pass-through under v2 minimal-validation: the validator does not enforce them, but renderers and pitch flows consume them.

Step 3: Write the blueprint JSON

Write the JSON file directly to the output path. Use this schema:

{
  "version": "1.0",
  "meta": {
    "title": "...",
    "industry": "retail",
    "revisionId": "rev-YYYYMMDD-NN",
    "parentRevisionId": null,
    "lastModifiedAt": "ISO8601",
    "lastModifiedBy": "ai"
  },
  "context": {
    "goals": [],
    "scope": [],
    "assumptions": [],
    "constraints": [],
    "sourceRefs": [{"type": "inline-text", "excerpt": "..."}],
    "clarifyRequests": [],
    "clarifications": []
  },
  "library": {
    "capabilities": [
      {"id": "cap-xxx", "name": "...", "level": 1, "description": "...", "ownerActorIds": [], "supportingSystemIds": []}
    ],
    "actors": [
      {"id": "actor-xxx", "name": "..."}
    ],
    "flowSteps": [
      {"id": "flow-xxx", "name": "...", "actorId": "actor-xxx", "capabilityIds": ["cap-xxx"], "systemIds": [], "stepType": "task", "inputRefs": [], "outputRefs": []}
    ],
    "systems": [
      {"id": "sys-xxx", "kind": "system", "name": "...", "aliases": [], "description": "...", "resolution": {"status": "canonical", "canonicalName": "..."}, "capabilityIds": ["cap-xxx"]}
    ]
  },
  "relations": [
    {"id": "rel-xxx", "type": "supports", "from": "sys-xxx", "to": "cap-xxx", "label": "支撐"}
  ],
  "views": [],
  "editor": {"fieldLocks": {}, "theme": "enterprise-default"},
  "artifacts": {}
}

Step 4: Generate visualizations

python scripts/business_blueprint/cli.py --export <blueprint.json>

This generates SVG + HTML viewer by default. Use --format drawio|excalidraw|mermaid for other formats.

Export View Selection Policy

Treat export view choice as a routing decision, not a styling preference.

• If a request matches a supported, standard export template, use that template.
• If there is no standard export template for the requested diagram, fall back to freeflow.
• Do not substitute swimlane, matrix, product tree, or other generic views just because they are available.
• When embedding a blueprint diagram into a report or ad hoc analysis, freeflow is the safe default unless the user explicitly asks for a supported standard template.

Step 5: Generate downstream projection

python scripts/business_blueprint/cli.py --project <blueprint.json>

This generates solution.projection.json, the canonical machine projection consumed by downstream report/slide workflows.

Workflow Decision Tree

User provides raw requirements / meeting notes?
  → AI agent reads hints, extracts entities, writes blueprint JSON
  → Optionally run --project for downstream machine handoff
  → Then run --export for visualization

User needs diagram files (SVG, draw.io, etc.)?
  → --export (default: SVG + HTML viewer)

User unsure about blueprint quality?
  → --validate

User wants downstream report / slide generation?
  → --project

Commands

Execution: Run directly as scripts:

python scripts/business_blueprint/cli.py --plan ...
python scripts/business_blueprint/cli.py --export ...

Export Formats

Collaboration Boundary

This skill produces semantic intermediate artifacts. Downstream skills consume them:

• report-creator consumes solution.projection.json → assembles reports
• slide-creator consumes solution.projection.json → assembles presentations
• Other skills may consume relations → generate PlantUML or other diagram syntax
• Downstream skills should never directly edit solution.blueprint.json
• solution.handoff.json is viewer-only metadata, not a downstream narrative input

Sandbox Execution

When running in an isolated Python sandbox (Jupyter, notebook, cloud REPL) that auto-installs dependencies:

1. The sandbox uses scripts directly. Run execution scripts from the repository root: python import subprocess subprocess.run(["python", "scripts/business_blueprint/cli.py", "--export", "solution.blueprint.json"])
2. sys.path.insert(0, os.path.dirname(os.path.abspath(__file__))) — will raise NameError
3. subprocess.run(["business-blueprint", ...]) — sandbox runs Python cells, not shell
4. os.system() — same reason

Architecture Diagram Generation

When user requests an architecture diagram (keywords: "架構圖", "architecture diagram", "--export", "diagram"):

1. Read references/architecture-design-system.md for the complete design system.
2. Read the appropriate template from references/architecture-templates/ based on the user's domain:
3. AWS/Serverless/Lambda → serverless.md
4. Microservices/Kubernetes/微服務 → microservices.md
5. Other → use serverless.md as a structural reference
6. Read the blueprint JSON to extract entities and flow steps.
7. Generate a self-contained HTML file with inline SVG following the design system rules.
8. Write the output file to the same directory as the blueprint JSON.

If the request does not match one of the supported standard templates above, stay on the default freeflow export path. Do not switch to another generic view type as a fallback. If a standard template would create a squeezed, clipped, or overcrowded diagram, stop using the fixed template geometry and fall back to freeflow or a wrapped multi-row layout.

Route eligibility matrix

Use an explicit route contract before rendering:

Do not invent route heuristics ad hoc inside a renderer. Route eligibility must stay explicit and reviewable.

Generation Rules

• Use dark mode by default (#020617 bg + 40px grid). Only use light mode when the user explicitly asks for it.
• L→R data flow: Clients(左) → Frontend → Backend → Database(右)
• Map systems[].category to semantic colors from the design system
• Map systems[].properties.type == "aws" → AWS Region boundary box
• Map systems[].properties.type == "k8s" → Kubernetes Cluster boundary box
• Use flowSteps[].seqIndex for L→R ordering
• Component sizing: 0-1 cap = small(44px h), 2-4 = medium(80px h), 5+ = large(80px h)
• Layout must be content-driven. Never force every node in a layer into one fixed row if that creates toothpaste-style squeezing.
• When a layer has more than 3 peer nodes, or labels/features become tight, wrap into multiple rows or widen the canvas before shrinking the content.
• Render users/actors as actor labels, badges, or lane headers by default. Do not render them as ordinary system cards unless the user explicitly asks for that visual treatment.
• Legend must live in a bottom safe area and participate in canvas sizing. Never place the legend as a floating overlay in the top-right corner.
• Final SVG/HTML height must be derived from the bottom-most node, legend, summary cards, and footer plus padding. Do not use fixed-height wrappers or overflow: hidden that can clip the last row.
• Z-order: bg → grid → title → region → arrows → nodes → legend → cards → footer
• Component border: rx="8", stroke-width="2"
• Region border: rx="16", stroke-dasharray="8,4", opacity="0.4"
• Geometry-sensitive integrity checks must use the numeric thresholds from evals/export-integrity-thresholds.json, not prose heuristics.

Output

• Single HTML file: {blueprint_stem}.html alongside the blueprint JSON
• No external dependencies (except Google Fonts CDN for JetBrains Mono)
• Opens in any browser, printable to PDF

Error Handling

• If --validate returns errors: fix structural issues before proceeding to --export.
• If --validate returns only warnings: proceed but note the warnings in any handoff.
• If Python version < 3.12: the package will refuse to install. Use python3 -m business_blueprint.cli with system Python as fallback.
• If a specialized route fails integrity: fall back to its configured fallback route.
• If freeflow also fails integrity: export exits non-zero with a structural diagnostics payload instead of emitting a silently broken artifact.

Cross-Platform Scope

Phase 2 does not attempt full Windows terminal parity.

Known deferred cases: - PowerShell pipe quirks beyond documented CLI contract tests - console-default encoding issues outside explicit UTF-8 execution paths

Accepted workaround for encoding-sensitive runs:

Use scripts directly (pure Skill, no package structure)

subprocess.run(["python", "scripts/business_blueprint/cli.py", "--export", str(blueprint_path)]) - set PYTHONIOENCODING=utf-8 where needed

這是一個功能完善、質量較高的 Skill。它能將售前需求快速轉化為視覺化的業務藍圖，支援匯出多種圖表格式，且內建驗證和修訂機制保障輸出質量。文件詳盡（中英雙語），使用簡單。主要優點是設計規範、匯出格式豐富、質量控制到位；不足是部分文件說明略有瑕疵，新使用者可能對行業選擇存在困惑。整體而言，這是一個值得信賴的生產級工具。