Write a precise task for a coding agent
A clear brief for a coding agent: goal, limits and acceptance criteria, so it changes no more than needed.
- Type
- Template
- Level
- Intermediate
- Time
- about 6 min
Results depend on the tool, the model and what you enter.
Fill in
What you type stays in this browser window. We store and send nothing.
- The sign-up form shows errors right next to each field
- The export writes CSV with semicolons
- The home page loads images only when scrolled into view
- A new API endpoint returns the last ten orders
- Search ignores upper and lower case
- src/components/forms
- app/export
- templates/index.html
- api/orders
- lib/search
- the database migrations
- the build configuration
- anything under vendor
- the public API
- the dependencies in package.json
- there is a new unit test for the case
- the page loads in the browser with no console errors
- the export matches a sample file
- the response arrives in under 200 ms
- no new linter errors appear
Your prompt
Task: [Goal]. Area affected: [Area]. Do not touch: [Off limits]. Acceptance criteria: - [Done when] - All existing checks still pass. Approach: first read the affected files and write a short plan. Wait for my OK before changing any files. Keep the change as small as possible and, at the end, summarise what you changed and why.
Matching tools
Tools from our catalog that this prompt works well with.
- Claude Code Prices and limits
- OpenAI Codex Prices and limits
- Cursor Prices and limits
How to use it
- Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
- Copy the finished prompt into a tool of your choice.
- Read the agent's plan critically before you agree, and review the diff yourself at the end.
Works in these tools
Prompts work in many chat and generator tools. This selection comes from our catalog; prices as shown on the tool page.
- Claude Code Prices on the tool page
- OpenAI Codex Free plan
- Cursor Free planfrom 8 USD per month
- GitHub Copilot Free planfrom $10
Why does this work?
Goal, limits and a checkable result are what a person needs in a ticket too. The plan-first step catches misunderstandings before any code is written.
Tips
- Keep the template in the repository so the whole team writes tasks the same way.