Practical Application

Consider two workflow problems.

The first is repeated keyword research. The useful outcome is not a document explaining keyword research. It is a tool that accepts information about a niche and returns relevant keywords through a usable interface. The task brief should therefore state both the domain requirement and the product requirement: the results must be relevant to the supplied niche, and the final output must be an application that can be operated directly.

The second is repeated sales-call review. The useful outcome is not a generic summary of a call. It is a system that analyzes team calls and gives improvement feedback based on an existing sales process. The existing process is part of the context; without it, the feedback cannot be aligned to how the team is expected to sell.

A practical design sequence is:

1. Write down the repeated task.
2. Name the final artifact.
3. List the information the agent must know.
4. State what would make the output acceptable.
5. Run a first version.
6. Inspect whether the output solves the original time problem.
7. Refine the task or save the workflow for reuse.