Enterprise Process Diagram

Purpose

Turn authorized process or architecture information into one presentation-ready .svg diagram and one editable .dot source file. A Mermaid code block, prose explanation, or unrendered plan alone is not a completed delivery.

Pattern

• Inversion to resolve missing actors, nodes, relationships, boundaries, and exceptions.
• Generator to produce the normalized diagram specification and files.
• Reviewer to verify structure, labels, readability, and file integrity.
• Pipeline to keep intake, payment, generation, and review in order.

Responsible roles: business process analyst and information designer.

Required Inputs

Collect before creating a paid order:

• diagram purpose and target audience
• diagram type: process, system architecture, data flow, responsibility flow, or organization relationship
• complete node list with stable ids and labels
• directed relationship list with source, target, and optional relationship label
• source material or source labels that authorize the structure

Prefer to collect:

• direction: left-to-right or top-to-bottom
• node kinds: actor, system, data, action, or decision
• grouping boundaries and confidential labels
• brand primary color and accent color

Do not charge when the purpose, audience, nodes, relationships, or source material is missing.

Workflow

1. Separate confirmed nodes and relationships from assumptions and unresolved questions.
2. Normalize duplicate names, assign stable ids, and identify missing start, end, owner, exception, or data boundary information.
3. Consolidate all paid-call inputs into one stable request body and complete the SkillPay flow.
4. Only after paid authorization succeeds, create a JSON specification that follows input-schema.md.
5. Generate the real files with node scripts/build-diagram.cjs --input <spec.json> --output <diagram.svg> from this Skill directory.
6. Verify that the SVG opens, every node and relationship is present, and the companion DOT source is generated.
7. Review against review-checklist.md before delivery.

Representative use cases are in marketplace-cases.md.

SkillPay / X402 Paid Service

Endpoint: POST https://www.yunqingqi.com/v1/skillpay/invoke

First request body:

{
  "skill_id": "enterprise-process-diagram",
  "skill_version": "1.0.0",
  "request_id": "a unique stable id of at least 8 characters",
  "query": "the consolidated purpose, audience, diagram type, direction, nodes, relationships, groups, sources, brand colors, and constraints"
}

Paid-call rules:

1. Confirm the Agent supports HTTP calls, weixinpay_pay, local file writing, and Node.js. Otherwise stop without charging.
2. Send the first request only after all required inputs are complete.
3. On HTTP 402, save WeixinPay-Required and X-Out-Trade-No.
4. Call weixinpay_pay(paymentCode=WeixinPay-Required) and wait for user-authorized payment.
5. Retry the exact same body with both saved headers after payment succeeds.
6. Generate the complete SVG and DOT only after the retry returns HTTP 200 with code: SUCCESS.
7. Never change the query, version, or request id on the paid retry. Reuse the same order after uncertain failures.
8. Never expose merchant credentials, private keys, payment parameters, or internal support notes.

Fail-Closed Payment Boundary

• HTTP 200 with code: SUCCESS is the only authorization to generate the complete diagram.
• On HTTP 401, 403, 404, 429, or any 5xx response, stop and report that the paid service is temporarily unavailable.
• If HTTP 402 lacks either required payment header, stop without charging.
• If payment is cancelled, times out, or returns an uncertain result, do not generate files and do not create a new order.
• Never replace a failed paid call with a free unrendered diagram.

Output

Deliver in this order:

1. clickable path or attachment for the final .svg
2. editable .dot source path
3. node count, relationship count, and canvas size
4. source labels used and unresolved items
5. generation manifest path

The generator writes <diagram>.dot and <diagram>.manifest.json beside the SVG.

Review Gate

• The diagram must contain 2 to 30 nodes and 1 to 60 relationships.
• Every relationship endpoint must reference a declared node.
• Labels must be readable, concise, and free of placeholders.
• Direction, grouping, ownership, and exception paths must match the approved source material.
• The SVG must open as valid XML and the DOT source must contain the same node and relationship counts.
• No internal path, token, credential, node address, or other tenant's data may appear.
• A human must confirm sensitive labels and external distribution.

Forbidden Actions

• Do not invent systems, approvals, owners, dependencies, data flows, or exceptions.
• Do not upload confidential diagrams to an unapproved external service.
• Do not insert Yunqingqi advertising into a customer's diagram unless requested.
• Do not automatically publish, email, or embed the diagram in an external system.
• Do not expose private prompts, internal infrastructure, API keys, node details, or other tenants' data.

Pricing Guidance

• Launch price: RMB 0.99 per call.
• One call covers one diagram with up to 30 nodes and 60 relationships, plus one correction pass.
• Explain the limit before payment. Do not silently split one diagram into multiple paid calls.

Human Gate

Stop and ask for confirmation before publishing this Skill, changing its price, uploading confidential customer material, or distributing the diagram externally.