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

# Review System

> Approve tasks or request changes with feedback

When a Claude agent finishes, the task moves to **Testing**. The review system lets you evaluate the work and either approve it or send it back for revisions.

<Frame>
  <img src="https://mintcdn.com/bahri/LhHfZeA1RQn4U7C6/images/feature-review.svg?fit=max&auto=format&n=LhHfZeA1RQn4U7C6&q=85&s=ae644af813b4252e58db5d42ce2b60ea" alt="Review System" width="900" height="320" data-path="images/feature-review.svg" />
</Frame>

## Review Actions

<Tabs>
  <Tab title="Approve">
    Click **Approve** to mark the task as done. The task moves to the **Done** column and no further agent work happens.
  </Tab>

  <Tab title="Request Changes">
    Provide written feedback explaining what needs to change. Claude Board spawns a new agent session with your feedback appended to the original prompt. The task moves back to **In Progress**.

    ```
    The login endpoint works, but:
    - Missing input validation on email field
    - Password should require minimum 8 characters
    - Add rate limiting to prevent brute force
    ```
  </Tab>
</Tabs>

## Feedback Loop

The revision cycle can repeat as many times as needed:

<Steps>
  <Step title="Claude finishes → Testing">
    Review the changes in the terminal log or your IDE.
  </Step>

  <Step title="Request changes with feedback">
    Describe what's missing or wrong. Be specific — Claude performs better with clear instructions.
  </Step>

  <Step title="Claude iterates → Testing">
    The agent picks up your feedback, makes adjustments, and returns to Testing.
  </Step>

  <Step title="Approve → Done">
    When satisfied, approve the task.
  </Step>
</Steps>

## Revision History

Every revision is recorded. The task detail view shows:

* Each round of feedback you provided
* The agent session logs for each iteration
* Token usage per revision
* Total cumulative cost

<Tip>Write feedback as if you're doing a code review. Bullet points with specific file or function references help Claude make targeted fixes.</Tip>

## Best Practices

<AccordionGroup>
  <Accordion title="Be specific in feedback">
    Instead of "this doesn't work," say "the `/api/users` endpoint returns 500 when the email field is missing."
  </Accordion>

  <Accordion title="Review before approving">
    Check the git diff or terminal logs. Claude may have made changes beyond what you expected.
  </Accordion>

  <Accordion title="Use small, focused tasks">
    Large tasks with vague descriptions lead to more revision cycles. Break work into smaller pieces.
  </Accordion>
</AccordionGroup>