# Review Your AI Agent’s Plan Before It Builds: Project Review in Prisment

> Approve the specs, diagrams and API contracts your AI agent builds from, see what it changed, decide each point, and hand back a review it reads first.

- Canonical: https://prisment.io/blog/review-ai-plans-before-they-are-built/
- Published: 2026-10-03
- Updated: 2026-10-04
- Author: Prisment Team (Documentation & Developer Tooling)
- Publisher: Prisment, https://prisment.io/

**Project Review lets you approve the documents your AI agent will build from, see exactly what it changed since, decide each point, and hand back a review file the agent reads before it starts.** It works on any folder, needs no AI model and no git, and writes nothing into your project unless you save the review yourself.

## 1. Why review the plan, not only the code

**An agent builds what its plan says, so the cheapest place to catch a wrong decision is the plan.** Requirements, an architecture note, a flow diagram and an API contract decide what gets written; a mistake there is a paragraph to fix, not a pull request to unpick. Prisment already draws those documents properly — diagrams, tables, OpenAPI specs — and Project Review adds the part a reader cannot do by eye: what changed, what is still open, and a record of what was agreed.

![An AI agent's plan open in Prisment: the booking flow drawn as a diagram and the prices as a table](https://prisment.io/images/blog/ai-markdown-plan.png)

## 2. Start a review in a minute

**Choose Review on the activity bar, open Project Review, name what you are approving, choose the documents, and start.**

1. **Open the folder** the agent writes to — in the desktop app, or in Chrome or Edge.
2. **Project Review → New review.** Say what decision it supports, and what an approval permits next: *Design*, *Task planning* or *Implementation*.
3. **Choose files or whole folders.** A folder also catches documents the agent adds later. Hidden spec folders such as `.kiro/` are listed.
4. **Start review.** Prisment reads what is saved on disk as the starting point; if a chosen file has unsaved edits, it asks first.

## 3. See what the agent changed

**After the agent has worked, press Refresh: each changed document shows before and after, word by word.** Added, removed and renamed documents are listed too, and a document that could not be read is called that — never *removed*.

![Project Review after the agent edited the plan: one added line in the booking flow, and an open question waiting for a decision](https://prisment.io/images/blog/ai-markdown-review.png)

## 4. What it checks, and what it never claims

**Every check is structural: it says what is there, never whether the design is right.**

| Check | What it finds |
| :--- | :--- |
| Links | links that lead to no file, or to more than one |
| Open items | `TODO`, `TBD`, entries under *Open questions*, unchecked boxes outside a task list |
| Contracts and diagrams | an OpenAPI or JSON Schema file that does not parse, a Mermaid diagram that does not draw |
| Spec layouts | the file a Kiro or Spec Kit spec expects but lacks; an ADR missing a section |

Code blocks, quotes and changelogs are left alone, so an example `TODO` is not reported. A clean result reads *no open items or issues found in N documents checked* — not *ready*.

## 5. Decide, comment, approve

**Each item gets your call — accepted, deferred, intentional or needs work — and a reason if you want one.** Comments go on the whole review, one document, one passage, or two passages that disagree; a comment follows its quote when the text moves and is marked outdated, with its original quote, when the words are gone.

**Approve** reads the documents once more and approves exactly those versions; if anything moved while you were reviewing, it approves nothing and says so. Change an approved document later and the review shows *Approval lapsed*.

## 6. Hand it back to the agent

**The review is one Markdown file that opens with a note to the agent: the status, what it may do next, what is blocked, and a SHA-256 hash of each approved document.** Only an approval for implementation says building may proceed, and the file never pretends approval is enforced.

**Share** holds every way to hand it on, the same in the document, the sidebar and Project Review:

- **Copy it** into the agent's chat, **download** it, or **save it** in the project where the agent will read it.
- **Send a colleague a link.** The review travels after the `#`, which browsers never send to a server, and nothing records the link. They can read it without Prisment, or import it into their own review.
- **Import a colleague's review** from their file or the link they send back. Comments and decisions merge by id; where you disagree, you choose.

Every check, option and the hash rule are in the guide: [Reviewing a project](https://prisment.io/help/#reviewing-a-project).

## Questions this article answers

### How do I see what my AI agent changed in a plan since I last read it?

Start a Project Review in Prisment over the plan and the documents around it. It keeps a starting point on your computer, and Refresh shows every document changed, added or removed since, with each change before and after. No git repository is needed.

### Does Project Review need an AI model?

No. The starting point, the comparison, the checks, your decisions and the review file all work with no model installed and no network connection. The checks are structural: links, open items, contracts, diagrams and spec layouts.

### Can Prisment review a Kiro or Spec Kit spec?

Yes. Choose the spec folder — hidden folders such as .kiro/ are listed — and the review reports a file the layout expects but the folder lacks, such as tasks.md, alongside the changes and open items in the spec itself.

### How does the AI agent learn what I approved?

From the review file: one Markdown file you copy into the chat or save in the project. It opens with a note to the agent stating the status, what it may do next, what is blocked, and a SHA-256 hash of each approved document. Only an approval for implementation says building may proceed. The approval is advisory: nothing forces an agent to read it.

### Is a shared review link uploaded anywhere?

No. The review travels inside the link after the #, a part of the address browsers never send to a server, and the page that opens it reports nothing to analytics. It carries paths, quotes, decisions and comments, never your documents.