plugins/cartograph/skills/workflow-diagram/SKILL.md
Generates a Mermaid workflow diagram showing process steps, decisions, and state transitions. Use when documenting CI/CD pipelines or lifecycle processes.
npx skillsauth add athola/claude-night-market workflow-diagramInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a Mermaid flowchart showing process workflows, pipelines, or state machines from code or documentation.
Dispatch the codebase explorer agent:
Agent(cartograph:codebase-explorer)
Prompt: Explore [scope] and return a structural model.
Focus on process steps, conditional logic, state
transitions, and pipeline stages for a workflow diagram.
Look for: Makefiles, CI configs, hook chains, command
sequences, and lifecycle methods.
Transform the structural model into a Mermaid flowchart with decision nodes and process steps.
Rules for workflow diagrams:
flowchart TD for sequential processesflowchart LR for pipelines with parallel tracks[Rectangle] for process steps{Diamond} for decision points([Stadium]) for start/end states[[Subroutine]] for sub-processes((Circle)) for join/sync points-->|label| for transition conditions-.->) for error/fallback paths==>) for critical pathExample output:
flowchart TD
start([Start: PR Created])
lint[Run Linters]
test[Run Tests]
review{Code Review}
approve[Approved]
changes[Request Changes]
merge([Merge to Main])
start --> lint --> test
test --> review
review -->|pass| approve --> merge
review -->|fail| changes -.-> lint
Call the Mermaid Chart MCP to render:
mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
prompt: "Workflow diagram of [scope/process]"
mermaidCode: [generated syntax]
diagramType: "flowchart"
clientName: "claude-code"
If rendering fails, fix syntax and retry (max 2 retries).
Show the rendered diagram with a brief description of the workflow stages and decision points (2-3 sentences).
tools
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
testing
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
development
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
testing
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.