- Home
- Skills
- Leegonzales
- Aiskills
- Process Mapper
process-mapper_skill
- Python
20
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill leegonzales/aiskills --skill process-mapper- CHANGELOG.md342 B
- README.md1.3 KB
- SKILL.md9.2 KB
Overview
This skill maps workflows, extracts SOPs, and identifies automation opportunities through a structured discovery-to-delivery workflow. It grounds an SOP-first doctrine: document actual work, expose tacit knowledge, and use tractability assessments to prioritize automation. Deliverables include process maps, SOP documents, automation zone analyses, and implementation roadmaps.
How this skill works
Run a diagnostic to determine SOP state (fiction, nonexistent, accurate) then follow a five-round process discovery interview to capture high-level flow, step decomposition, decision points, edge cases, and context dependencies. Document the process in the most appropriate format (linear SOP, decision tree, swimlane, or visual diagram), mark tacit knowledge and exceptions, then classify each step on a two-axis tractability grid. Finally, analyze automation opportunity zones, prioritize by pain × feasibility, and produce ROI-backed roadmaps.
When to use it
- Document a process that has no reliable SOP
- Conduct process discovery interviews with teams or individuals
- Create SOPs from tacit knowledge and shadow processes
- Assess which tasks are good candidates for automation
- Prioritize automation projects based on ROI and feasibility
Best practices
- Capture the actual current state, not the aspirational process
- Use the five-round interview: flow → decomposition → decisions → exceptions → context
- Label tacit decision points (black box) instead of forcing HOW details
- Include frequency, volume, and pain metrics to inform prioritization
- Validate maps with the process owner and iterate
Example use cases
- Map customer onboarding to reveal manual handoffs and quick RPA wins
- Document expense approval SOP and identify rule-based automation zones
- Interview support team to surface tacit triage rules for copilot design
- Analyze reporting workflows to separate data-gathering (automatable) from insights (human)
- Prioritize a portfolio: quick wins first, strategic investments second
FAQ
Document that a decision exists and its trigger/impact without trying to codify tacit judgment; this preserves visibility and enables future training or automation work.
How do you decide documentation format?
Choose linear SOP for short sequential tasks, decision trees for branching logic, swimlanes for multi-role handoffs, and visual diagrams for complex system integrations.