Starter briefs
Twelve briefs, ready to file
A brief is the short piece of text you type to hand a job to an agent: what you want, and how you'll know it's done. Copy one, change the specifics, then file it as a task.
Filing good work starts with knowing what a small, checkable brief looks like. Each page below carries a real one you can copy, plus what to have on hand before you file it and how you'll know it landed. New to the word "task"? The glossary defines it in plain English, and writing tasks covers the fuller set of rules these briefs already follow.
Clear the bug backlog
Send the small bugs nobody has time for to an agent, and get them fixed the same day.
A control that is cut off on a phone
File the button or menu that gets clipped on a narrow screen, and get it fixed.
For a developerA label that is wrong in one place only
Name the one screen where a label or copy string says the wrong thing, and get it corrected everywhere it needs to be.
Cover untested code
Point an agent at a file with no tests, and get a real test suite back instead of a promise to write one later.
Keep the docs true
Have an agent check a doc page against the code it describes, and fix the parts that drifted.
Ship a small feature
File one idea in plain words, and get a working feature back with a pull request instead of a spec nobody built.
Pay down a refactor
Apply one convention across a whole repo, file by file, without stopping other work to do it.
Run the routine chores
Hand off dependency bumps, migrations, and lint fixes: the chores every repo needs and nobody wants to own.
Have your own job in mind?
These twelve are starting points, not the only shape a brief can take. Write your own the same way: what you want, and how you'll know it's done.