A **proposal** is the agent's plan for an idea: one or more documents (a PRD, a technical
design) plus a set of **task drafts** with their dependencies. Nothing is built until you
read that plan and approve it — this is the decision gate at the heart of the
[Reversed Conversation](/guides/ai-dlc-workflow/). This guide covers reading a submitted
proposal and either approving or rejecting it.

## Find the proposal

From the project sidebar, select **Proposals**. The page lists proposals on a board; a
badge shows how many are **pending review**. A proposal the agent has submitted for you
carries a **Pending Review** status. Select it to open its detail page.

## Read the documents and task drafts

The detail page shows everything you need to judge the plan:

- **Description** — the proposal's summary and the source idea(s) it is **Based on**.
- **Document Drafts** — the PRD, technical design, or spec the agent wrote. Read these for
  the *what*, *why*, and *how*.
- **Task Drafts** — the units of work the proposal will create. Each draft shows its
  acceptance criteria count and how many other tasks it depends on. Together the drafts and
  their dependencies form the execution graph.
- A **Details** sidebar (status, input type, creator, timestamps), **Source Ideas**, and
  any attached **References**.

As you read, check that the documents describe the requirement clearly, the tasks cover it
without scope creep, each task has clear acceptance criteria, and the dependency order makes
sense. Use the discussion drawer to leave comments or ask the agent to clarify.

![Proposal detail page with document drafts and task drafts awaiting review](/images/workflow/proposal-review.webp)

## Approve or reject

Open the **Actions** menu in the top-right of the proposal. For a proposal that is pending
your review you can:

- **Approve** — a dialog lets you add an optional note for the proposal's creator before you
  confirm. Approving accepts the plan.
- **Reject** — a dialog requires a reason. Rejecting sends the plan back so the agent can
  revise the drafts and resubmit. Be specific: name the document gaps or the tasks whose
  acceptance criteria need work, so the next version fixes exactly those.

:::note[What the agent does]
The agent authored these documents and task drafts after elaboration resolved, and submitted
them for your review. If you reject, the same agent revises the drafts against your feedback
and resubmits. You approve or reject; the agent does the drafting and revising. See the
[agent platforms reference](/reference/agents/) for how that connection works.
:::

## What approval creates

Approving is the moment the plan becomes real work. From the drafts, Chorus **creates**:

- Each **document draft** becomes a real **Document**, visible under the project's
  **Documents** section.
- Each **task draft** becomes a real **Task** with status **Open**, ready to be claimed or
  assigned, and its draft dependencies become real task dependencies.

The idea's displayed status advances automatically from the new proposal and tasks — you do
not update it by hand. If an approved proposal later proves wrong, the **Actions** menu also
offers **Revoke Approval**, which closes the tasks it created, deletes the documents it
created, and returns the proposal to draft.

![Proposal Actions menu with Approve, alongside the tasks it will create as Open](/images/workflow/proposal-approve.webp)

## Next

With the tasks created and open, continue to [Run tasks](/guides/run-tasks/).