All products

Document the current workflow with AI

Record the way a process operates today, including workarounds, decision points and handoffs. Stable step IDs make it easier to reconcile conflicting accounts later.

Document the current workflow with AI before a redesign workshop changes everyone’s view of the old process. The okhp3-as-is-process-capture skill builds a structured baseline from a process intake record and supplied evidence. It separates activities, events and decisions, assigns stable identifiers and records how well the current description is supported.

A procedure might say that a purchase goes straight to approval. Interviews might reveal a manual check against a separate list. Capture that step, its role and its evidence, then leave the disagreement with the written procedure visible. A future-state proposal can refer back to the same step without changing the baseline.

What it does

  • Sequence the activities that take place in practice.
  • Record a decision gateway and the routes it opens.
  • Associate a handoff with role and system information.
  • Give an unresolved step a traceable reference.
  • Preserve gaps in current-state evidence for follow-up.

Install and use

  1. Install the skill and supply a process intake record in the expected format, plus authorised evidence such as role-based interview notes. The optional local ID helper needs Node.js.
  2. Ask, “Capture the current purchase-approval workflow. Record manual checks as described and flag the points the sources disagree about.”
  3. Walk through the resulting baseline with the people who perform the work before using it as a comparison point.

FAQ

Source

Made by OverKill Hill P³. Original skill: okhp3-as-is-process-capture, published on GitHub under the MIT licence.

View on GitHub