agentleFS
peter-tu-zynkrpeter-tu-zynkr/zynkr-skill-builder/skills/2-sales-consultant/consult-flow-design/SKILL.md

consult-flow-design

Skill21 starsChanged 50 days agoNo licenceView on GitHub

Visualize a consulting engagement's operations on Lucid as a paired AS-IS / TO-BE process chart set — drawn from the engagement's own documents (session notes, 痛點 ledgers, [Plan] docs, BRD) and recorded back on the CRM deal. ALL drawing, editing, and lint mechanics are delegated to the installed product-flow-design skill; this wrapper adds engagement resolution, the as-is/to-be pairing discipline, chart naming, and CRM linkage. Trigger on /consult-flow-design or when Peter says "畫客戶的 as-is/to-be 流程", "客戶流程圖", "幫這個案子畫流程", "把客戶流程視覺化", "map the client's operations on Lucid", "visualize the engagement workflow", or "draw the as-is and to-be for this client". Distinct from product-flow-design (the generic Lucid specialist — any chart, no engagement context; a pasted Lucid URL with no client context still routes THERE), from consult-solution-planning (produces the [Plan] narrative this skill draws), and from operations-flow-optimization / operations-transformation (they design the flow's CONTENT; this skill only visualizes what the engagement documents already say).

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.