agentleFS
45ck45ck/business-analysis-skills/.agents/skills/to-be-process-designer/SKILL.md

to-be-process-designer

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Start from the business goal and current-state pain points.

    line 33
  2. Distinctive:

    Document what changes, what stays, and why.

    line 35
  3. Distinctive:

    Prefer structured outputs over loose prose.

    line 51
  4. Distinctive:

    Do not pretend weak evidence is confirmed fact.

    line 56
  5. Distinctive:

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

    line 57
  6. Distinctive:

    Do not hide missing coverage behind polished wording.

    line 58
  7. 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

to-be-process-designer

Purpose

Design an improved future-state process with clearer roles, fewer pain points, and explicit transition implications.

Trigger this skill when

  • The current process has been analyzed and future-state design is needed.
  • Stakeholders want improvement options rather than only problem documentation.
  • A change initiative needs a future workflow view.

Expected inputs

  • as-is process findings
  • business goals
  • constraints
  • stakeholder preferences
  • risks

Deliverables

  • to-be process outline
  • changes from current state
  • transition risks
  • open design decisions

Operating procedure

  1. Start from the business goal and current-state pain points.
  2. Propose a future-state workflow with revised roles, decisions, handoffs, and controls.
  3. Document what changes, what stays, and why.
  4. Highlight transition, adoption, and dependency risks.
  5. List open design decisions and unresolved tradeoffs.

Quality gates

  • The future-state process solves named pain points.
  • Differences from current state are explicit.
  • Transition implications are visible.

Handoff targets

  • benefit-hypothesis-writer
  • raci-rasci-builder
  • architecture/design packs later

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.