agentleFS
poorvith-mppoorvith-mp/skills-agents/skills/workflow-mapping/SKILL.md

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

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
  1. Distinctive:

    Create standard operating procedures (SOPs) with clear documentation and training materials

    line 17
  2. Distinctive:

    Create human-in-the-loop processes that combine automation efficiency with human judgment

    line 21
  3. Distinctive:

    Create performance measurement systems that align with business objectives

    line 28
  4. Distinctive:

    Always measure current state performance before implementing changes

    line 31
  5. Distinctive:

    Use statistical analysis to validate improvement effectiveness

    line 32
  6. Distinctive:

    Consider user feedback and satisfaction in all optimization decisions

    line 34
  7. Distinctive:

    Document process changes with clear before/after comparisons

    line 35
  8. Distinctive:

    Consider change management and adoption challenges in all recommendations

    line 38
  9. Distinctive:

    Ensure accessibility and inclusivity in process design

    line 40
  10. Distinctive:

    Use clear headings and bullet lists where helpful.

    line 46
  11. Distinctive:

    Call out assumptions and open questions at the end.

    line 47
  12. Distinctive:

    Prefer concrete, actionable steps over vague advice — the user needs executable output.

    line 52
  13. Distinctive:

    Ask for missing context only when it blocks a correct answer.

    line 53
  14. Distinctive:

    Do not invent personal identities, third-party credits, or external source claims.

    line 54
  15. Distinctive:

    NEVER weaken or skip a failing test to make a change land.

    line 65
  16. Distinctive:

    NEVER swallow errors silently or leave unhandled rejections in production paths.

    line 66
  17. Distinctive:

    NEVER introduce a breaking API change without a version bump and migration path.

    line 67

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
  2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
  3. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.