ワンクリックでManusで任意のスキルを実行

okhp3-mermaid-bpmn

スター3

フォーク0

更新日2026年6月23日 04:17

BPMN-informed business process modeling in Mermaid. Use whenever the user wants to diagram a business process, workflow, approval chain, decision/gateway logic, swim lanes, cross-department handoffs, onboarding flows, procurement flows, or anything describable as "who does what, in what order, with what decision points." This is the differentiator no community Mermaid skill covers — BPMN vocabulary (gateways, events, tasks, swim lanes, subprocesses) does not exist in mgranberry, WH-2099, softaworks, or Agents365's skills. Always load okhp3-mermaid-core first for audience/type/theming, then this skill for BPMN vocabulary and patterns.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

OKHP3

OKHP3/mermaid-diagram-bpmn

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

OKHP3 Mermaid BPMN

BPMN 2.0-informed semantics, expressed in Mermaid syntax. Loaded after okhp3-mermaid-core has handled audience declaration and type selection.

Swim Lanes

Encoded via subgraph per lane (department/role), with direction set per lane to control internal flow. See references/swimlane-layouts.md for horizontal vs. vertical lane patterns and crossing-reduction specific to multi-lane diagrams.

Gateways

Four types, each with a distinct visual encoding (node shape/style, not just a label):

Exclusive (XOR) — one path taken, mutually exclusive conditions
Parallel (AND) — all paths taken simultaneously
Inclusive (OR) — one or more paths taken based on conditions
Event-based — path determined by which event occurs first

Full encoding patterns, including how to label branch conditions for Analyst-tier diagrams, in references/gateway-patterns.md.

Events

Start, intermediate, end, timer, message, error, signal, terminate. Each gets distinct node styling (not just different labels) so the diagram is isomorphic to BPMN semantics even when read by someone who knows BPMN notation. Catalog in references/bpmn-elements.md.

Tasks

User task, service task, script task, send/receive task. Distinct shapes per type — this is what makes a diagram "argue" rather than "display" (per the core design philosophy). Catalog in references/bpmn-elements.md.

Subprocesses

Collapsed (single node, expandable) vs. expanded (inline detail) vs. call activity (reference to a separate diagram). When a subprocess becomes its own diagram, register the cross-reference in DIAGRAMS.md (per core's naming-conventions.md) and note it on both diagrams. Patterns in references/subprocess-patterns.md.

Annotations & Associations

Text annotations and dashed association lines for adding context without implying flow. Catalog in references/bpmn-elements.md.

Process instance vs. process definition

Be explicit about which is being diagrammed. A process definition shows all possible paths; a process instance shows one actual run through it. Mixing these in one diagram is a common source of Gate 2 (semantic) failures.

Worked examples

references/process-examples/ contains validated .mmd examples (approval-flow, onboarding, procurement) once authored. Currently empty — Phase 1 deliverable.

このリポジトリの他の Skills

同じリポジトリ

okhp3-foundry-repo-creator

OKHP3/mermaid-diagram-bpmn

Create governed FoundRy child repositories from Custom GPTs, Gemini Gems, Copilot agents, prompt bundles, Notion concepts, research notes, or prototype ideas. Use whenever the user wants to migrate an AI capability into GitHub, standardize a repo, create a child repo scaffold, or convert platform-specific AI work into a reusable capability package.

2026-06-263

okhp3-skill-foundry

OKHP3/mermaid-diagram-bpmn

OverKill Hill P³ Skill Foundry -- complete eight-phase methodology for creating, honing, and polishing production-quality Agent Skills. Activate when asked to create a new skill from scratch, hone or polish an existing skill, apply OKHP3 brand attribution, design live evals, run executor subagents for benchmarking, grade responses with evidence-anchored expectations, compute benchmark deltas, or iterate based on eval failures. Also activate when someone wants to turn a workflow into a distributable skill, needs to benchmark a skill's with-skill vs without-skill gap, wants a professional quality bar for a SKILL.md, or asks about the OKHP3 skill authoring process. This is the authoritative Foundry methodology for any skill creation or honing work in this repo -- use it even when the user just says "make a new skill" or "improve this skill" without mentioning the Foundry by name.

2026-06-263

okhp3-as-is-process-capture

OKHP3/mermaid-diagram-bpmn

Capture and normalise a current-state process description into a structured as-is process YAML with stable step identifiers. Use this skill when the user has a process that is already running and needs to document its current state before gap analysis or redesign; when they provide step lists, SOPs, or process notes that need to be structured; when they say "document what we do today", "capture the current process", or "baseline the process before we change it". Produces a structured as-is process artifact with normalised step IDs.

2026-06-243

okhp3-decision-model-authoring

OKHP3/mermaid-diagram-bpmn

Author and validate decision models from PNS decision points using DMN-aligned rule tables. Use this skill when the PNS contains three or more gateway decision points that warrant a structured decision table; when the user asks to document business rules as decision logic, build a DMN table, or make decision criteria explicit. This is a recommended extension skill triggered automatically when visual-process-modeling identifies three or more gateways. Produces a decision-model YAML and a human-readable DMN rule table.

2026-06-243

okhp3-elicitation-and-interview-facilitation

OKHP3/mermaid-diagram-bpmn

Plan and facilitate structured elicitation sessions using BABOK v3 interview and workshop techniques. Use this skill when you need to gather process knowledge from subject matter experts; when the user wants a question plan before an interview or workshop; when elicitation is incomplete and gaps need targeted follow-up; when they say "help me interview the process owner", "prepare questions for the workshop", or "what should I ask to fill in the missing steps". Produces a question plan and elicitation notes template.

2026-06-243

okhp3-future-state-and-change-strategy

OKHP3/mermaid-diagram-bpmn

Design a target-state process and a structured change strategy from a gap analysis. Use this skill when the user wants to redesign a process after gaps have been identified; when they ask "what should the process look like", "how do we fix this", "design the to-be process", or "build a change plan". Produces a future-state process artifact and a change strategy document. This is a recommended extension skill — use after process-gap-and-exception-analysis has produced a gap analysis. Scope firewall applies: never include employer-proprietary constraints without explicit user authorisation.

2026-06-243

name

okhp3-mermaid-bpmn

description

OKHP3 Mermaid BPMN

BPMN 2.0-informed semantics, expressed in Mermaid syntax. Loaded after okhp3-mermaid-core has handled audience declaration and type selection.

Swim Lanes

Gateways

Four types, each with a distinct visual encoding (node shape/style, not just a label):

Exclusive (XOR) — one path taken, mutually exclusive conditions
Parallel (AND) — all paths taken simultaneously
Inclusive (OR) — one or more paths taken based on conditions
Event-based — path determined by which event occurs first

Full encoding patterns, including how to label branch conditions for Analyst-tier diagrams, in references/gateway-patterns.md.

Events

Tasks

Subprocesses

Annotations & Associations

Text annotations and dashed association lines for adding context without implying flow. Catalog in references/bpmn-elements.md.

Process instance vs. process definition

Worked examples

references/process-examples/ contains validated .mmd examples (approval-flow, onboarding, procurement) once authored. Currently empty — Phase 1 deliverable.