# Twelve briefs, ready to file

Twelve briefs ready to file: plain-language starter text for two small, bounded jobs under each of CodeHerder's six use cases.

Source: https://codeherder.com/starter-briefs/

Starter briefs

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.

[Request access →](https://codeherder.com/get-started/#request-access) [See the six jobs →](https://codeherder.com/use-cases)

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](https://codeherder.com/glossary/task) defines it in plain English, and [writing tasks](https://codeherder.com/docs/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.

[No code needed 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.](https://codeherder.com/starter-briefs/control-cut-off-on-phone/) [For a developer A 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.](https://codeherder.com/starter-briefs/label-wrong-in-one-place/)

[Read the full job page →](https://codeherder.com/use-cases/clear-the-bug-backlog/)

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.

[No code needed Add a missing test for a bug that shipped Name the bug that already got fixed, and get a test that makes sure it can't come back unnoticed.](https://codeherder.com/starter-briefs/test-for-a-shipped-bug/) [For a developer Cover the one file nobody has tests for Name a file with no test coverage, and get a real test suite for what it actually does.](https://codeherder.com/starter-briefs/cover-the-untested-file/)

[Read the full job page →](https://codeherder.com/use-cases/cover-untested-code/)

Keep the docs true

## Have an agent check a doc page against the code it describes, and fix the parts that drifted.

[No code needed One doc page no longer matches the product Point at the doc page and the feature it describes, and get the drifted parts corrected.](https://codeherder.com/starter-briefs/doc-page-out-of-date/) [For a developer A code example in the docs no longer runs Point at the broken example, and get a version that actually runs against the current code.](https://codeherder.com/starter-briefs/code-example-that-no-longer-runs/)

[Read the full job page →](https://codeherder.com/use-cases/keep-the-docs-true/)

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.

[No code needed Add a field to a form we already have Name the field, where it should live on an existing form, and get a working save-and-show for it.](https://codeherder.com/starter-briefs/add-a-field-to-a-form/) [For a developer Add a filter to a list we already have Name the list and what you want to narrow it by, and get a working filter control for it.](https://codeherder.com/starter-briefs/add-a-filter-to-a-list/)

[Read the full job page →](https://codeherder.com/use-cases/ship-a-small-feature/)

Pay down a refactor

## Apply one convention across a whole repo, file by file, without stopping other work to do it.

[No code needed One thing has two names; give it one Name the two terms that mean the same thing, and get the whole codebase moved to one of them.](https://codeherder.com/starter-briefs/give-one-thing-one-name/) [For a developer Pull one duplicated block into one place Point at the same logic copied into more than one place, and get it merged into one shared version.](https://codeherder.com/starter-briefs/pull-duplicated-code-into-one-place/)

[Read the full job page →](https://codeherder.com/use-cases/pay-down-a-refactor/)

Run the routine chores

## Hand off dependency bumps, migrations, and lint fixes: the chores every repo needs and nobody wants to own.

[No code needed Bump one dependency and fix what breaks Name the dependency and the version, and get an upgrade with whatever it breaks already fixed.](https://codeherder.com/starter-briefs/bump-one-dependency/) [For a developer Delete a dead flag and every reference to it Name the flag that always resolves one way now. Get it and its dead branch removed.](https://codeherder.com/starter-briefs/delete-a-dead-flag/)

[Read the full job page →](https://codeherder.com/use-cases/run-the-routine-chores/)