Creating good tasks

Producta can be used to solve tickets or to refine them.

These are some general tips on how to define tasks to obtain the best results for both flows.

​

To solve tasks

Let’s start with this simple task about adding some tests, which we want Producta to directly solve, and see how we can improve it to obtain better results:

1. Be clear: state the problem or solution at hand focusing on making it clear and unambiguous:

2. Point at the relevant code: if you are defining a technical solution, be as specific as you can about which files, classes or functions need to be updated:

​

To refine tasks

Now let’s discuss how to better create tickets defining ideas or projects, that we want Producta to help us refine into technical tasks. Consider this vague task about creating an integration with Linear:

1. Be elaborate: explain what the idea or project is about, what are its features and how it will be used.

2. Iterate: the best way to refine a large task is normally to divide it into smaller, more precise tasks. When Producta’s AI recommends this, the best move forward is to create the new tasks, and keep refining them using Producta if needed.