business-workflow-doc — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited business-workflow-doc (Agent Skill) and scored it 87/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 3 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 3 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Generate visual Mermaid flowcharts from exploration session captures and session briefs.
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, or sequenceDiagram--title TEXT : Optional diagram titlepython 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.mdThe 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
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.<example> Context: User has completed problem framing and BRD draft. user: "Can you map out the checkout flow based on what we've captured?" assistant: "I'll use business-workflow-doc to generate a Mermaid flowchart from your BRD draft." </example>
<example> Context: User wants to visualize a state machine. user: "Document the order status workflow as a state diagram." assistant: "I'll use business-workflow-doc with --type stateDiagram to map the order lifecycle." </example>
<example> Context: Brownfield re-entry, documenting existing system behavior. user: "Map the current approval process before we redesign it." assistant: "I'll run business-workflow-doc against the current-system capture to produce a baseline flowchart." </example>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.