Writing a good task

It can take a little while to find the right balance on what a good task is, but in general they shouldn't be too big, focused on one area at the time and have a clear definition of done. Definition of done is taken from Agile and is a set of conditions that must be true in order to consider a task done.

Remember that AI is a lot better at specific and structured prompts rather than open-ended instructions. "Write 3 paragraphs" is better than "write some text".

A good task

This task is good because it is directive and clearly defines what functionality you want, without mixing too many domains at at the same time. The tasks scope is limited and it's clear for the agent what needs to be done for this task to be considered done.

Title:

Create a reusable component for generating PDF reports.

Description:

Create a reusable component where I can send in a PDF report design and view it in the UI as a PDF.
I should also be able to download the PDF.

Definition of Done:
- I can generate a PDF report
- I can download the PDF report
- A demo page has been created where I can view an example of the component in use

A bad task

While the agent might be able to solve this task, especially if you're app is relatively small, it's not clear how to solve it and neither when this task is done. The task is open-ended and suggestive.

Title

Create a PDF report from my companies style and design

Description

Add a way of generating PDFs that match my companies style and design