Business workflow doc
Skill richfrem/agent-plugins-skills/plugins/exploration-cycle-plugin/skills/business-workflow-doc
repo for reusable plugins and skills
npx -y skills add richfrem/agent-plugins-skills --skill business-workflow-docAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate Mermaid flowcharts documenting business processes, state machines, and workflow logic from session captures. Use when you need to map multi-step processes, approval flows, user journeys, or decision trees during exploration. Trigger with "map this workflow", "create a process diagram", "flowchart the business process", "document this workflow", or "visualize the state machine".
SKILL.md
3.6 KB, as published. Nobody here has run it
Business Workflow Documentation
Generate visual Mermaid flowcharts from exploration session captures and session briefs.
Usage
python ./scripts/generate_workflow.py \
--input <capture_file_or_glob> \
--output <output_file.md> \
--type <flowchart|stateDiagram|sequenceDiagram>
Flags:
--input PATH: Input file(s) — session brief, BRD draft, or problem framing capture--output PATH: Output markdown file (default:exploration/captures/workflow-map.md)--type TYPE: Diagram type:flowchart(default),stateDiagram, orsequenceDiagram--title TEXT: Optional diagram title
Capture Pass (CLI dispatch pattern)
python scripts/dispatch.py \
--agent .agents/skills/exploration-cycle-plugin-requirements-doc-agent/SKILL.md \
--context exploration/session-brief.md exploration/captures/brd-draft.md \
--instruction "Mode: workflow-map. Generate a Mermaid flowchart diagram of the core business process described in this context. Use a flowchart TD layout. Label each step clearly. Include decision nodes for branches and validation gates." \
--output exploration/captures/workflow-map.md
Output Format
The skill always outputs a Markdown file with one or more fenced Mermaid code blocks:
# Business Workflow: [Process Name]
Source: [input file(s)]
Date: [today]
## Core Process Flow
```mermaid
flowchart TD
A[Start: Trigger Event] --> B{Validation Gate}
B -->|Pass| C[Step 1: Process Action]
B -->|Fail| D[Error: Notify User]
C --> E[Step 2: Business Rule Applied]
E --> F{Approval Required?}
F -->|Yes| G[Approval Workflow]
F -->|No| H[Auto-Proceed]
G --> I[End: Complete]
H --> I
```
## Open Questions
- [NEEDS HUMAN INPUT] (step ordering unclear from captures)
Diagram Types
| Type | Use When |
|---|---|
flowchart | Sequential multi-step processes with decision branches |
stateDiagram | Object lifecycle states (e.g., order status transitions) |
sequenceDiagram | Service-to-service or user-to-system interaction flows |
Anti-Hallucination Rules
- Do NOT invent process steps not described in the source captures.
- If step ordering is ambiguous, list the options and mark
[NEEDS HUMAN INPUT]. - Do NOT add error handling paths unless explicitly mentioned in the source.
- Mark every diagram as
DRAFTuntil confirmed by the human explorer.