Process Documentation
Copyright (c) 2026 KunAgent. Licensed under the MIT License.
Purpose
Turn an operational process into a clear SOP, role model, control map, and improvement backlog.
Tool routing
| Tool or skill | Use |
|---|---|
show_diagram |
Publish a complex process diagram. |
show_visualization |
Show a short flow or grouped explanation. |
design_create_diagram |
Create a process diagram on Design canvas. |
Workflow
- Define trigger, outcome, scope, owner, participants, systems, inputs, and exceptions.
- Interview the process through concrete recent examples.
- Map the current state before designing the target state.
- Document steps, decisions, controls, handoffs, evidence, and exception routes.
- Add RACI, metrics, review cadence, and change ownership.
Completion gates
- Walk one normal case and one exception case end to end.
- Ensure each decision has an owner and each control has evidence.
- Separate current process from proposed improvements.
Boundaries
- Do not hide unresolved ownership behind vague team labels.
- Do not add automation or policy requirements without an accountable owner.
Delivery
Lead with the outcome, name the evidence used for verification, and disclose any real limitation that remains.