---
title: "Briefs"
description: "A specification an agent works from — draft it, refine it with context, approve it, then start an implementation."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.trevize.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Briefs

A **brief** is a specification: a document that describes what to build. Instead
of handing an agent a one-line prompt, you write a brief, refine it with real
context, approve it, and then start a [task](/concepts/tasks) from it — so the
agent works from a clear, reviewed spec.

## The editor

A brief has an editable **title** and a markdown/rich-text **body** that
autosaves as you type and supports real-time collaborative editing with
`@mentions`. A side **chat assistant** helps you draft: it can search your GitHub
issues, repositories, and files and read file contents to ground the brief in
your actual codebase.

## Status: draft → approved → archived

Every brief has a status you control:

- **Draft** — a work in progress.
- **Approved** — reviewed and ready to build. Implementation is only enabled once
  a brief is approved.
- **Archived** — set aside.

## Attaching context

A brief can reference **resources** — GitHub repositories and Linear issues or
projects — to give the agent the surrounding context it needs.

## From brief to implementation

When a brief is **approved**, choose **Implement** to open the *Start
Implementation* dialog: pick the repository, an optional base branch, a model,
and the blueprint. Trevize links the resulting [implementation](/concepts/tasks)
back to the brief, and the brief lists its implementations so you can track them.

> **Why write a brief?**
>
> Briefs pay off for larger or higher-stakes work: a reviewed spec produces more
> predictable results than an off-the-cuff prompt, and it gives your team a shared
> artifact to align on before any code is written.

Source: https://docs.trevize.dev/concepts/briefs/index.mdx