Give the task a destination.
A mission brief connects an observed problem to a result someone can verify. It gives an AI coding assistant enough context to make local decisions without making up product requirements. Start with the failure or missing behavior, then define the smallest useful outcome.
Describe the observable difference
Replace "improve error handling" with a concrete case: a malformed import should show a field-specific message and leave existing records untouched. Include reproduction steps and the relevant input shape. Remove private values from examples while preserving the conditions that trigger the problem.
Define the limits of the mission
Name the likely module, compatibility requirements, and behaviors that must remain stable. Specify which checks would establish success. If a decision requires product knowledge, call it out before implementation. Avoid prescribing file edits before the assistant has inspected the relevant code.
Checkpoint
- Current and desired behavior stated
- Acceptance evidence defined
- Unresolved product decisions named
Read-only transmission
Investigate [observed behavior]. Desired result: [specific outcome]. Preserve [existing contract]. First locate the responsible code and propose a bounded change. Validate with [reproduction or test]. Stop and report if the fix requires [excluded decision].
A brief is complete when a reviewer could judge the result without reconstructing the conversation that produced it.
Next: Change boundaries