# Write a no-code automation specification from a manual process **trustWF workflow pack** · IT & Business Automation ## Outcome A tool-neutral automation brief covering trigger, inputs, logic, approvals, exceptions, data handling and acceptance checks. ## Who this is for Operations teams and automation builders documenting a repeatable workflow ## What to provide Current process steps; process owner; systems and approved connectors; record types; volume; exceptions; permissions; success criteria. Do not paste credentials, access tokens or real sensitive records. ## Steps 1. Map the current process, actors, systems, inputs and outputs. 2. Separate deterministic rules from judgment or approval steps. 3. Specify trigger, conditions, routing, failure handling, audit trail and data retention needs. 4. Define test cases and acceptance criteria for a safe pilot. ## Copy-ready instructions Stage 1 — Prepare and diagnose When to use: Before doing the work, use this stage to check source quality, definitions, scope and critical missing information. Copy and paste: You are a careful, tool-neutral assistant helping operations teams and automation builders documenting a repeatable workflow. Help me write a no-code automation specification from a manual process. Use only the information I provide. Separate confirmed facts, assumptions and suggestions. Never invent figures, source claims, commitments or policy. Ask no more than three essential questions if missing facts would change the result; otherwise use clearly marked placeholders. Keep language plain. Remove or mask personal and confidential information before use. Context: [organization, role and situation] Source material: [paste only information you are permitted to share] Constraints or policy: [format, time, rules and approvals] Stage 1 — Prepare and diagnose Clarify the current process and approved systems. Identify high-impact actions, sensitive data and exceptions that require human judgment. Return: A brief input check, missing-information list and any essential questions. Do not hide uncertainty. Mark missing facts as questions or placeholders. Expected output: A brief input check, missing-information list and any essential questions. Check before continuing: Check that the period, units, source and decision boundary are correct. Stage 2 — Analyze and plan When to use: Use this stage after the inputs are ready. Carry forward the Stage 1 input check and supplied material. Copy and paste: You are a careful, tool-neutral assistant helping operations teams and automation builders documenting a repeatable workflow. Help me write a no-code automation specification from a manual process. Use only the information I provide. Separate confirmed facts, assumptions and suggestions. Never invent figures, source claims, commitments or policy. Ask no more than three essential questions if missing facts would change the result; otherwise use clearly marked placeholders. Keep language plain. Remove or mask personal and confidential information before use. Context: [organization, role and situation] Source material: [paste only information you are permitted to share] Constraints or policy: [format, time, rules and approvals] Stage 2 — Analyze and plan Translate the process into a step table: trigger, input, rule, action, owner, exception, retry and log. Keep unknown connector capabilities as questions; do not assume a tool can do something. Return: A traceable analysis or plan with calculations, rules and uncertainty stated. Do not hide uncertainty. Mark missing facts as questions or placeholders. Expected output: A traceable analysis or plan with calculations, rules and uncertainty stated. Check before continuing: Check formulas, definitions, priorities and evidence before using the draft. Stage 3 — Produce and review When to use: Use this stage after you accept the analysis. Carry forward prior outputs and correct any facts before finalizing. Copy and paste: You are a careful, tool-neutral assistant helping operations teams and automation builders documenting a repeatable workflow. Help me write a no-code automation specification from a manual process. Use only the information I provide. Separate confirmed facts, assumptions and suggestions. Never invent figures, source claims, commitments or policy. Ask no more than three essential questions if missing facts would change the result; otherwise use clearly marked placeholders. Keep language plain. Remove or mask personal and confidential information before use. Context: [organization, role and situation] Source material: [paste only information you are permitted to share] Constraints or policy: [format, time, rules and approvals] Stage 3 — Produce and review Produce a tool-neutral specification, swimlane-style step sequence, required permissions, failure and rollback behavior, data handling notes, pilot scope and acceptance tests. Return: The requested draft plus assumptions, unresolved questions, a review checklist and one next action. Do not hide uncertainty. Mark missing facts as questions or placeholders. Expected output: The requested draft plus assumptions, unresolved questions, a review checklist and one next action. Check before continuing: Verify facts, policy, calculations and required human approval before acting. ## Review before using Do not bypass security, permissions, human approvals or retention policies. Avoid unrestricted write access and credential sharing. IT/security and process owners must approve the design and test it outside production. --- Use the result as a draft. Review it for accuracy, context and any required approvals.