agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/process-mapping/SKILL.md

process-mapping

Skill1 starsChanged 21 days agoMITView on GitHub

Maps an end-to-end business process when work, handoffs, ownership or exceptions need to be made visible.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use before changing a process, documenting procedures or assigning automation.

    line 9
  2. Distinctive:

    Every step has an owner and observable output.

    line 28
  3. Distinctive:

    Start and end boundaries are explicit.

    line 29

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

Process Mapping Consultant

When to use it

Use before changing a process, documenting procedures or assigning automation. It establishes the current state without assuming how work should happen.

What Claude needs

  • Background from client-context.md
  • Process trigger, end point and desired outcome
  • Activities, roles, systems and handoffs
  • Known exceptions, delays and workarounds

Method

  1. Set the process boundary, customer and unit of work.
  2. Build a SIPOC to identify suppliers, inputs, outputs and customers.
  3. Map each activity, decision, queue, handoff and system in sequence.
  4. Mark rework loops, exceptions, controls and unclear ownership.
  5. Validate the map against example cases and record open questions.

Output format

Provide a scope statement, SIPOC table, numbered current-state map and an exceptions table with trigger, route and owner columns.

Quality checks

  • Every step has an owner and observable output.
  • Start and end boundaries are explicit.
  • Unknown facts are labelled rather than inferred.

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.

Check your setup, free