AI agency in Dubai · a free AI skill every morning at 6:00 Gulf time
AskWisely.ai
0126ClaudeAutomation2 min read

Spec the Workflow Before You Automate It

You get a plain, checkable specification of a manual process that your builder can turn into an automation without guessing.

Automations get built from a quick conversation, so they cover the normal case and break on the first exception nobody mentioned. The fixes then take longer than the original build, and the team quietly goes back to doing it by hand.

That is the gap this drop closes. It is a automation skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.

Who should use it

Operations managers and team leads who want a recurring task automated but are not the ones building it.

How it works

The skill file does five things, in this order.

1. Pick one recurring process. Choose a task your team does the same way every week, such as logging new orders or routing supplier invoices. Name the person who owns it.

2. Write down today's steps. Have the person who actually does the task list each step, the systems they touch and the choices they make. Paste it as written, without tidying it.

3. Add real cases, including failures. Paste two or three real examples, with at least one that needed special handling. These give Claude the material for decision rules and exceptions.

4. Answer the open questions. If Claude stops and lists missing information, get the answers from the process owner and run it again. Check every line tagged [INFERRED] before accepting it.

5. Hand the spec to your builder. Give the finished specification to whoever builds the automation and ask them to run every test case before going live. Keep the spec as the reference when something changes.

What comes back

A structured specification covering trigger, inputs, numbered steps, decision rules, exceptions routed to named people, outputs, test cases and open questions, with every inference tagged.

The mistake to avoid

The common mistake is describing only the happy path, the way the task runs on a good day, and leaving out the cases that went wrong. Always paste at least one messy real example, because that is where the decision rules and exceptions come from.

Running it

Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.

The prompt

Claude · SKILL.md
You are writing an automation specification for a small business team. The process is {process_name}, owned by {process_owner}. We plan to build it in {automation_tool}.

Here is how the work is done today:
<current_process>
{paste how the task is done now, step by step, including who does what and which systems or files are used}
</current_process>

Here are real examples of the process:
<sample_cases>
{paste two or three real cases, including at least one that went wrong or needed special handling}
</sample_cases>

Produce a specification with these sections, in this order:
1. Trigger: the exact event that starts the workflow.
2. Inputs: every field the workflow needs, its source system and its format.
3. Steps: numbered, one action per step, naming the system that performs it.
4. Decision rules: each branch written as "If X, then Y", with the threshold or value stated.
5. Exceptions: cases that must go to a person, who receives them and what information they are sent.
6. Outputs: what is created or updated, and where.
7. Test cases: one test per decision rule and per exception, drawn from the sample cases where possible.
8. Open questions.

Rules:
- Use only what the description and samples state. Where you infer a step, rule or field, tag it [INFERRED] and say what it is based on.
- If the trigger, the required inputs or the owner of exceptions cannot be determined from the material, list what is missing under Open questions and stop. Do not write the Steps section on a guess.
- Do not add automation beyond the process described.
- Write in plain English that a non-technical manager can check line by line.
Share this skill
Newsletter

The daily skill, in your inbox

One email each morning with the new drop. Unsubscribe in one click.

One email each morning. Unsubscribe in one click. We never sell or share your address.