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".
From exploration-cycle-pluginnpx claudepluginhub richfrem/agent-plugins-skills --plugin exploration-cycle-pluginThis skill is limited to using the following tools:
evals/evals.jsonevals/results.tsvscripts/generate_workflow.pyGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Configures Istio traffic management with VirtualServices, DestinationRules for routing, canary/blue-green deployments, circuit breakers, load balancing, and fault injection in service meshes.
Generate visual Mermaid flowcharts from exploration session captures and session briefs.
python3 ./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, or sequenceDiagram--title TEXT : Optional diagram titlecat exploration/session-brief.md exploration/captures/brd-draft.md \
| copilot -p "$(cat .agents/skills/exploration-cycle-plugin-requirements-doc-agent/SKILL.md)" \
"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." \
> exploration/captures/workflow-map.md
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]
| 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 |
[NEEDS HUMAN INPUT].DRAFT until confirmed by the human explorer.