How to write a workflow for one job

Name one job

Start with a job a person already repeats. A report, a research pass, a draft that has to cite its sources, a review that should not depend on whoever is free. Write the name of the job, who touches it, and what done looks like.

If you cannot point at the task, the files, and the person who has to trust the result, stop. A one-off chat with a model is not a workflow yet. Do not invent a new process so a model has something to do.

Write the inputs

• The source material: files, notes, sites, tickets, transcripts, or spreadsheets.
• The checks a person already applies before the work is trusted or sent.
• The tools the job may call, and the ones it must not.
• The artifact someone should be able to open and reuse.

Bound the tools

Search, an API, a database, a browser action, or an agent belongs in the workflow only when the job needs it. Write what it may read and what it may not change. If a person still has to trust the output, the workflow does not send or publish on its own.

The homepage shows a report as an example of this shape: notes, a ticket list, and a brief go in, and a cited draft comes out. That card is an example.

Leave a check a person can repeat

Write the instructions the job reuses, the place a person checks the output, and one first run someone can inspect. The useful version is often shorter than the one you have. Cut the steps that do not change the artifact. If a step has to stay with a person, leave it there and say so.

You should be able to run the next one without a tour of model features. The handover is the workflow itself: the inputs, the bounds, the check, and the artifact.

Agent-ready pages and forms

When the job lives on a page, declare the form. A name, a plain description, and named fields let an agent call the form instead of guessing at the layout. A person still sees the same form.

First Look is that pattern on this site. The checks you can watch there, the title, the headings, declared tools, llms.txt, and robots.txt, are the checks to write down before a page is handed on. A send that changes something still waits for a person.