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

# Review and Spec Reports

> Nothing counts as done until you approve it, and bigger changes start with a Spec Report.

## Review

When your agent finishes a task, it moves it to Review, never straight to Completed. Open the task and choose:

* **Approve.** The task is marked Approved with today's date. Your agent then records it in Completed with its commit and removes it from Review.
* **Send back…** Add a note. The task goes back to the top of Current Sprint with the note and the date, so your agent sees what to fix when it picks the task up again.

Clicked the wrong one? Both can be undone.

## Spec Reports

Your agent checks the specs before it writes code, and how much it checks depends on the size of the change:

| Change | Examples | What happens first |
| - | - | - |
| Trivial | style, typo, config | No check. Your agent notes it in `tasks.md` afterwards. |
| Feature | a new component or behaviour | Your agent reads the relevant specs and updates requirements and tasks before coding. |
| Architectural | a new system, dependency or data model | Your agent updates every affected spec and the changelog, then shows you a Spec Report and waits. |

A Spec Report lists the kind of change, the files it touched, what changed in each and what the specs now say. Your agent writes no code until you reply with the exact words `yes, proceed`. You can ask for one at any time with `/specpilot-report`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.