Write a clear task for an agent

A good brief tells an agent what useful work looks like and tells you when to stop. Fill in the goal, files to inspect, existing work to preserve, relevant check and decisions that need separate approval.

Blank brief

# Task brief

## Goal

Describe one outcome.

## Scope

List the files or subsystem to inspect.

## Existing work

State which changes must be preserved.

## Acceptance

Name the relevant test or observable result.

## Approval boundary

List actions that need a separate decision.

Example: investigate before editing

Goal: explain why the empty-input parser test fails. Scope: read the parser and that test only. Existing work: preserve the current formatting edits. Acceptance: identify the disagreement and name the relevant test command; do not claim it passed without running it. Approval boundary: ask before editing, adding dependencies or sending project text to a new service.

Start with the investigation. If it identifies a correction, review a second brief for that change. A narrow task is easier to inspect than an open-ended instruction to improve the project.

The brief expresses intent. It does not restrict file permissions, enforce a budget or remove tools. Review the actual permissions separately.