Build a reusable workflow
A workflow describes a process in advance. Use one when the structure of the job is repeatable, even if the inputs change each time.
Start with a real example
Run the job once in chat and identify the steps that mattered. Separate information gathering, transformation, review, and external action. Give each step a clear expected output.
Define the flow
Open Workflows and use an available definition or author a process. Workflows can sequence steps, run independent work in parallel, branch on results, wait, and ask for human input. Use a review gate where a decision belongs to you.
Design a workflow that reads [input], produces a cited summary, checks it against the input, and waits for my approval before delivery. Define the expected output and failure behavior for each step.
Run and review
Start with a small input. Follow the run’s step states and inspect its artifacts. Waiting for input is different from failed or complete. A blocked run needs its missing dependency or decision resolved.
Edit carefully
Changing completed work can invalidate downstream results. Rewind the relevant part before editing when the interface requires it, and review any confirmation describing work that will run again. External side effects may need separate reconciliation; a rewind is not a guarantee that an external message or change has been undone.
Repeat or automate
Once the process works, reuse it with new input or connect it to a schedule. Review the first automated result before making it a routine.