Skip to content

Learn to write tickets

A ticket is how you ask your project’s agent for work, like “add a login page” or “switch the homepage hero to a video.” Small changes in how you write it make a big difference in what you get back.

Habit 1

Describe the outcome, not the implementation

Say what should be true when the work is done. Leave the how to the agent.

Harder to finish

Add a state variable and a loop that filters the array.

Easier to finish

Let visitors filter the template list by category, and keep their choice when they reload the page.

Habit 2

Say how you will know it is done

The better a ticket states the goal and how you would judge it done, the better the result.

Harder to finish

Make the signup page better.

Easier to finish

Make the signup page ask only for an email. When I submit it, I should see a confirmation message and land on my dashboard.

Habit 3

Point to real things

Reference the URLs or files you mean. For a bug, include the steps to reproduce it.

Harder to finish

Fix the bug where checkout fails.

Easier to finish

On /checkout, add any item, apply a coupon, and press Pay. The page shows a server error instead of the receipt.

Habit 4

Do not pre-decompose

Ask for the whole change in one ticket. The agent plans the steps, so you do not have to split the work first.

Harder to finish

Step 1: create the table. Step 2: add the form. Step 3: add the list page.

Easier to finish

Add a feature request board where people can post an idea and vote on others.

Habit 5

Pick the right mode

Use Investigate when you only want answers. It is read-only: no code changes and no deploy. Use a build ticket when you want the change made.

Harder to finish

Change the checkout code and see if that fixes it.

Easier to finish

Investigate why checkout fails when a coupon is applied. Do not change anything yet.

The examples are written for this guide. They are not recorded tickets.

Keep it moving

Writing the ticket is the first step. These guides cover what comes next.