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.
- 1. Describe the outcome, not the implementation
- 2. Say how you will know it is done
- 3. Point to real things
- 4. Do not pre-decompose
- 5. Pick the right mode
Habit 1
Describe the outcome, not the implementation
Say what should be true when the work is done. Leave the how to the agent.
Add a state variable and a loop that filters the array.
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.
Make the signup page better.
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.
Fix the bug where checkout fails.
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.
Step 1: create the table. Step 2: add the form. Step 3: add the list page.
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.
Change the checkout code and see if that fixes it.
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.
- Answer the agent when it asksA paused ticket shows an "The agent needs your input" card. The agent resumes within a few seconds of your reply.→
- Retry with notes when a ticket failsThe AI rewrites the ticket from the original, the summary and your notes. You can edit it before you confirm.→
- Check the estimate firstThe ticket dialog shows a typical and a high estimate before you send it.→
- Take control any timeYou cannot type while the agent works. Take control pauses the ticket so you can step in.→