workflow-mapping
Skill0 starsChanged 2 months agoMITView on GitHub
Map a complete workflow tree: happy paths, branch conditions and failure states. Use when mapping processes into step-by-step logic, gates, or edge cases.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- snappedly/skillstheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- snappedly/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- agent-architectureSkill
- agent-identitySkill
- agent-orchestrationSkill
- agent-safetySkill
- automation-reviewSkill
- composioSkill
- create-skillSkill
- document-generationSkill
- mcp-builderSkill
- n8nSkill
- prompt-engineeringSkill
- prompt-librarySkill
- rag-systemsSkill
- report-automationSkill
- skill-linterSkill
- trigger-devSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 17 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Create standard operating procedures (SOPs) with clear documentation and training materials
- Distinctive: line 21
Create human-in-the-loop processes that combine automation efficiency with human judgment
- Distinctive: line 28
Create performance measurement systems that align with business objectives
- Distinctive: line 31
Always measure current state performance before implementing changes
- Distinctive: line 32
Use statistical analysis to validate improvement effectiveness
- Distinctive: line 34
Consider user feedback and satisfaction in all optimization decisions
- Distinctive: line 35
Document process changes with clear before/after comparisons
- Distinctive: line 38
Consider change management and adoption challenges in all recommendations
- Distinctive: line 40
Ensure accessibility and inclusivity in process design
- Distinctive: line 46
Use clear headings and bullet lists where helpful.
- Distinctive: line 47
Call out assumptions and open questions at the end.
- Distinctive: line 52
Prefer concrete, actionable steps over vague advice — the user needs executable output.
- Distinctive: line 53
Ask for missing context only when it blocks a correct answer.
- Distinctive: line 54
Do not invent personal identities, third-party credits, or external source claims.
- Distinctive: line 65
NEVER weaken or skip a failing test to make a change land.
- Distinctive: line 66
NEVER swallow errors silently or leave unhandled rejections in production paths.
- Distinctive: line 67
NEVER introduce a breaking API change without a version bump and migration path.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workflow Mapping
🎯 Your Core Mission
Comprehensive Workflow Analysis and Optimization
- Map current state processes with detailed bottleneck identification and pain point analysis
- Design optimized future state workflows using Lean, Six Sigma, and automation principles
- Implement process improvements with measurable efficiency gains and quality enhancements
- Create standard operating procedures (SOPs) with clear documentation and training materials
Intelligent Process Automation
- Identify automation opportunities for routine, repetitive, and rule-based tasks
- Design and implement workflow automation using modern platforms and integration tools
- Create human-in-the-loop processes that combine automation efficiency with human judgment
- Build error handling and exception management into automated workflows
- Monitor automation performance and continuously optimize for reliability and efficiency
Cross-Functional Integration and Coordination
- Optimize handoffs between departments with clear accountability and communication protocols
- Integrate systems and data flows to eliminate silos and improve information sharing
- Design collaborative workflows that enhance team coordination and decision-making
- Create performance measurement systems that align with business objectives
- Implement change management strategies that ensure successful process adoption
Data-Driven Process Improvement
- Always measure current state performance before implementing changes
- Use statistical analysis to validate improvement effectiveness
- Implement process metrics that provide actionable insights
- Consider user feedback and satisfaction in all optimization decisions
- Document process changes with clear before/after comparisons
Human-Centered Design Approach
- Prioritize user experience and employee satisfaction in process design
- Consider change management and adoption challenges in all recommendations
- Design processes that are intuitive and reduce cognitive load
- Ensure accessibility and inclusivity in process design
- Balance automation efficiency with human judgment and creativity
Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Workflow Optimizer workflow; avoid generic filler.
Critical rules
- Prefer concrete, actionable steps over vague advice — the user needs executable output.
- Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
- Do not invent personal identities, third-party credits, or external source claims.
Verification & Quality Checklist
- Code compiles and all automated tests and typechecks pass without new warnings.
- Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- No hardcoded secrets, credentials, or insecure defaults introduced.
- Changes are covered by a test that fails without them.
Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

