Document a process with Claude before automating it
Document a process with Claude before automating it. Method, fictional example, expected files and checks before use.
By Educasium
Define a process with Process Interviewer →
A process connects a trigger, inputs, decisions and an output. The pack interviews to clarify these, exceptions and success criteria. Start with a real case rather than desired features. State who acts, using which information, and how the next step is decided. Reuse existing documents and flag contradictions. The interview should expose decisions rather than endlessly generate questions.
Prepare information
Goal, real example, current steps, participants and expected outcome. Identify versions and separate facts from assumptions before starting.
Fictional test example
Fictional example: a request arrives without a project number. Define whether it waits, returns to the requester or is assigned manually. “Process the request” does not describe that decision. Include the case and its owner in the plan.
Check the deliverable
Walk through the plan with someone who performs the process. Check normal, incomplete and external-failure cases. The pack can build a skill when requested; a planning-only interview should stop at the approved plan.
The linked skill page provides the download and practical steps.