agentleFS
45ck45ck/business-analysis-skills/.claude/skills/as-is-process-investigator/SKILL.md

as-is-process-investigator

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 and analyze the current-state process, including actors, steps, decisions, delays, pain points, exceptions, and unofficial …

    line 12
  2. Distinctive:

    Prefer structured outputs over loose prose.

    line 51
  3. Distinctive:

    Do not pretend weak evidence is confirmed fact.

    line 56
  4. Distinctive:

    Do not confuse stakeholder opinion with validated rule or process truth.

    line 57
  5. Distinctive:

    Do not hide missing coverage behind polished wording.

    line 58
  6. Distinctive:

    Do not flatten politically different stakeholders into one generic audience.

    line 59

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

as-is-process-investigator

Purpose

Document and analyze the current-state process, including actors, steps, decisions, delays, pain points, exceptions, and unofficial workarounds.

Trigger this skill when

  • You need to understand the current process before recommending change.
  • The real workflow is unclear or disputed.
  • There are complaints but no agreed process map.

Expected inputs

  • interview notes
  • observation notes
  • documents
  • current system/process context

Deliverables

  • as-is process summary
  • pain points
  • handoff map
  • gaps and risks
  • candidate modeling notes

Operating procedure

  1. Reconstruct the current workflow from multiple evidence sources.
  2. List actors, triggers, decisions, artifacts, handoffs, timings, and exception paths.
  3. Identify bottlenecks, rework loops, and dependency pain points.
  4. Separate official process from how work actually gets done.
  5. Summarize the current-state findings and what should be preserved, fixed, or questioned.

Quality gates

  • Official and unofficial workflows are separated.
  • Pain points are grounded in observed or reported evidence.
  • The output is specific enough to inform to-be design.

Handoff targets

  • to-be-process-designer
  • business-rule-extractor
  • benefit-hypothesis-writer

Output style

  • Be explicit about uncertainty.
  • Prefer structured outputs over loose prose.
  • Separate confirmed findings, inferred findings, and open questions.
  • Preserve source context where practical.

Failure modes to avoid

  • Do not pretend weak evidence is confirmed fact.
  • Do not confuse stakeholder opinion with validated rule or process truth.
  • Do not hide missing coverage behind polished wording.
  • Do not flatten politically different stakeholders into one generic audience.

Minimum output skeleton

## Summary
## Findings
## Structured outputs
## Risks or tensions
## Open questions
## Recommended next skill

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.