Give the agent a useful brief.
Describe the outcome, the constraints, and the failure behavior. Skip the elaborate prompt ceremony.
The prompts that help most are usually quite ordinary. They say what someone should be able to do, what must stay the same, and how to handle the awkward cases. You don’t need to guess the file names or write the implementation yourself.
Say what should happen.
“Add export” leaves several decisions open. Export which records? In which format? With the current filters? A better request answers the questions you already know the answer to.
Here’s a starting point. Adapt the screen and requirements to your project.
› /implement-feature let users export the invoices currently shown in the list as CSV. Include invoice number, customer, date, status, and total. Respect the active filters and current sort order.Name the things that must stay true.
An agent can make a request work while accidentally changing a contract you rely on. Say which behavior needs preserving. That might be an API response shape, a permission rule, a design pattern, or a dependency choice.
Don’t list every convention in the repository. Project instructions and existing code should already carry those. Mention the constraints that are easy to miss for this particular task.
› /implement-feature add a status filter to orders. Keep the existing pagination and response shape. Use our existing validation and error format. Don’t add a new dependency just for the filter.Describe the awkward case.
Most happy paths are easy to infer. Failure behavior often isn’t. Tell the agent what the user should see when a request times out, a list is empty, or a retry could create a duplicate.
You don’t have to enumerate every possible bug. Start with the failure that matters most to the feature.
› /implement-feature add retry to the failed import view. A retry should reuse the existing import request identity so it does not create a second import. Keep the failure details visible until the retry starts.Let real questions stay questions.
If you haven’t decided whether admins can see all projects, don’t disguise that as a technical detail. Ask for the options before implementation. This matters especially for permissions, data migrations, and public contracts.
If the request is straightforward, let the agent inspect the code and proceed. You shouldn’t have to approve an import statement. You should understand a change to who can access your data.
› /plan-change add organization invites. First identify the permission decisions we need to make, then propose a small implementation plan grounded in the current membership code.