Run any Skill in Manus with one click

new-process

Stars3

Forks1

UpdatedJuly 17, 2026 at 06:44

Scaffolds a new business process in this repository — creates a single BPMN file under the processes folder with a complete diagram (semantics + layout), lanes for the owning roles, and callActivity links to any sub-processes. Use when the process facts (trigger, outcome, roles, rough flow) are already known — from the user or a capture-process interview — and the user wants to add, scaffold, or start modeling a new process.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Miragon

Miragon/bpm-iq

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

new-process

description

New Process

Scaffold a process as a single .bpmn file. The slim content contract is just bpmiq.yml + .bpmn files: a process IS its BPMN, there is no process.yaml, no landscape, no INDEX. The process id is the file name without the extension.

Inputs to gather

From the user's request (ask only for what you cannot infer):

id — kebab-case, unique across the repo (the .bpmn file stem), e.g. order-to-cash.
name — human title; model it as the pool name so it is derivable.
trigger — the start event (object + past participle, e.g. "Order received").
outcome(s) — the end event(s).
happy path — the ordered steps between trigger and outcome.
roles — who does what → BPMN lanes (lane name = team/role label).
decisions — branch points → gateways phrased as questions.
sub-processes — steps complex enough to be their own .bpmn; link via a callActivity whose calledElement is the sub-process's id (its file stem).

Steps

Find the processes folder from bpmiq.yml (processes: key). Confirm the id is free: no existing <folder>/**/<id>.bpmn.
Write <folder>/<id>.bpmn — one <bpmn:process> (or a collaboration with one pool named after the process). Include:
- a laneSet with one lane per role, every flow node assigned to a lane;
- the flow: start event → tasks/gateways → end event(s), all sequenceFlows wired (sourceRef/targetRef);
- a complete bpmndi:BPMNPlane: a BPMNShape for every flow node, lane and pool, and a BPMNEdge for every sequence/message flow. Missing DI breaks the visual editor (Hard Rule).
For each sub-process, create a separate <folder>/subprocesses/<sub-id>.bpmn the same way, and reference it from the parent via <callActivity calledElement="<sub-id>">.
Follow the modeling conventions: tasks verb + object ("Check credit limit"), events object + past participle, gateways as questions ("Approved?").
Validate before finishing: node packages/validator/src/validate.ts --root . (from the monorepo root) — fix every error. The validator checks XML well-formedness, flow structure, BPMNDI coverage, and that each callActivity resolves to a real process.

Output

Report the new file path(s) and the derived view the platform will show (get_process via the MCP server, or deriveProcess): name, roles, steps, gateways, and sub-process calls. Do not invent metadata that is not in the model.

More from this repository

same repository

capture-process

Miragon/bpm-iq

Conversational process capture — interviews a process owner who cannot write BPMN, elicits trigger, outcome, happy path, decisions, handoffs, and exceptions one question at a time, plays the understood process back in plain language for correction, then hands the confirmed data to the new-process skill for scaffolding. Use when someone wants to talk through, describe, or explain how their process works, wants a process documented from an interview, says "let me tell you how we do X", or says they don't know BPMN.

2026-07-173

export-process-skill

Miragon/bpm-iq

Exports a business process — its BPMN model, any sub-processes it calls, and the derived process view — as a self-contained, portable agent skill under dist/skills/. Use when the user wants a process "as a skill", wants processes to be usable by other agents or projects, or says "let this process talk".

2026-07-173

import-process

Miragon/bpm-iq

Imports existing process documentation — draw.io or Visio XML, pasted Word/Confluence text, flowchart images the agent reads, PowerPoint exports — into the repository as a BPMN model. Extracts activities, decisions, and roles; generates a convention-conform .bpmn with a complete diagram layout; records provenance and runs the validator. Use when the user wants to import, convert, migrate, or digitize an existing process document, diagram, or wiki page.

2026-07-173

process-feedback

Miragon/bpm-iq

Files and triages reports that a process model no longer matches reality — the inbound channel of "let your processes talk". Use when someone says "that's not how we do it anymore", "this step is outdated", or "we skip that check now" (in any conversation, about any process), when the user pastes a PROCESS FEEDBACK block produced by an exported process skill, or when they ask to file, list, triage, accept, or reject process feedback. Owns the feedback/<id>/ inbox convention and drives accepted corrections through a model edit.

2026-07-173

process-navigator

Miragon/bpm-iq

Lets the user talk to the processes in this repository. Answers questions about modeled business processes — how a process works step by step, who does what (from the BPMN lanes), what it calls, and what is affected by a change. Use when the user asks about a process, a role/ownership question, an impact analysis, or wants a walkthrough.

2026-07-173

process-review

Miragon/bpm-iq

Quality gate for process models — runs the deterministic validator (BPMN structure + BPMNDI coverage + callActivity link integrity), then checks BPMN modeling conventions and diagram clarity by judgment. Use when the user asks to review, validate, lint, or check a process, before merging model changes, or for a portfolio health report.

2026-07-173

name

new-process

description

New Process

Inputs to gather

From the user's request (ask only for what you cannot infer):

id — kebab-case, unique across the repo (the .bpmn file stem), e.g. order-to-cash.
name — human title; model it as the pool name so it is derivable.
trigger — the start event (object + past participle, e.g. "Order received").
outcome(s) — the end event(s).
happy path — the ordered steps between trigger and outcome.
roles — who does what → BPMN lanes (lane name = team/role label).
decisions — branch points → gateways phrased as questions.
sub-processes — steps complex enough to be their own .bpmn; link via a callActivity whose calledElement is the sub-process's id (its file stem).

Steps

Find the processes folder from bpmiq.yml (processes: key). Confirm the id is free: no existing <folder>/**/<id>.bpmn.
Write <folder>/<id>.bpmn — one <bpmn:process> (or a collaboration with one pool named after the process). Include:
- a laneSet with one lane per role, every flow node assigned to a lane;
- the flow: start event → tasks/gateways → end event(s), all sequenceFlows wired (sourceRef/targetRef);
- a complete bpmndi:BPMNPlane: a BPMNShape for every flow node, lane and pool, and a BPMNEdge for every sequence/message flow. Missing DI breaks the visual editor (Hard Rule).
For each sub-process, create a separate <folder>/subprocesses/<sub-id>.bpmn the same way, and reference it from the parent via <callActivity calledElement="<sub-id>">.
Follow the modeling conventions: tasks verb + object ("Check credit limit"), events object + past participle, gateways as questions ("Approved?").
Validate before finishing: node packages/validator/src/validate.ts --root . (from the monorepo root) — fix every error. The validator checks XML well-formedness, flow structure, BPMNDI coverage, and that each callActivity resolves to a real process.