agentleFS
45ck45ck/business-analysis-skills/.agents/skills/process-modelling-and-improvement/SKILL.md

process-modelling-and-improvement

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Document the as-is process with tasks, flow, decisions, and handoffs.

    line 17
  2. Distinctive:

    Prefer evidence-backed conclusions over polished speculation.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Purpose

Understand the current process, surface pain points, and define an improved target process.

Use when

  • process inefficiency or inconsistency is a core issue
  • as-is/to-be modelling is needed
  • handoffs, roles, and decisions are not well understood

Inputs

  • project or problem context
  • goals and constraints
  • known stakeholders, systems, and documents
  • level of formality required

Procedure

  1. Define the business event, actors, boundaries, and outcome.
  2. Document the as-is process with tasks, flow, decisions, and handoffs.
  3. Identify bottlenecks, duplication, ambiguity, and failure points.
  4. Challenge assumptions and piecemeal modifications.
  5. Design the to-be process with explicit improvements.
  6. Compare as-is and to-be via a gap list.
  7. Capture benefits, risks, and change implications.
  8. Provide diagram-ready specs for UML activity or BPMN modelling.

Outputs

  • as-is process spec
  • to-be process spec
  • gap analysis
  • improvement actions
  • diagram instructions

Guardrails

  • Explicitly separate fact, inference, and assumption.
  • Prefer evidence-backed conclusions over polished speculation.
  • Where conflict exists, record it rather than smoothing it away.
  • Produce artifacts that can be inspected, edited, and reused.

Completion criteria

  • deliverable pack exists
  • tradeoffs are explicit
  • unknowns are logged
  • next decisions are obvious

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.