Refine specifications with the agent

Comment on the specs the agent drafted, then send the comments over. The agent reads them as refine instructions and rewrites those parts.

In the appVersion detail

On this page

Where to find it
Comment on what is off
Send them to the agent
Open, Sent, Resolved
Sync from the codebase

Maleus drafts your specification. Refining is how you ask it to change what it wrote. You never edit specs as files: you comment on what is off, and the agent rewrites those parts.

This lives inside the Specifications step of a guided version. It is not available on direct versions, which edit code straight away.

Where to find it

Open the version in development.
Pick the Specifications step in the header. The spec tree fills the main area, grouped into Functional, Backend and Frontend, each with its own count.
Open a spec. The Comments button in the document toolbar carries the number of open comments, and opens the panel on the right.

The Specifications step: a use case open, with the Comments panel listing an open request — Comment on the spec itself. The panel on the right keeps the list.

Comment on what is off

Two ways to leave a comment, and they behave the same afterwards:

Where	How	What you get
On a passage	Select the text, then Comment on this selection	A numbered marker links the comment back to that exact passage
On the whole document	Add a general comment at the top of the panel	A comment attached to the spec, with no anchor

Comments pile up in the Open tab. Nothing reaches the agent yet, so you can go through several specs and mark everything before you commit to a turn.

Keep each comment on one concern. "Add an export-to-CSV button to this table" works better than a multi-paragraph wishlist. You can send a first batch and open a second one straight after.

Send them to the agent

Tick the comments you want to send, or Select all, then send. Maleus asks you to confirm: Send {n} comments to the agent? The agent receives them as refine instructions, and the comments move to the Sent tab.

Sending several at once matters. The agent sees every requested change in the same turn, so it can keep the specs consistent across them rather than fixing one and breaking another.

The proposed updates flow back into the chat. From there you either accept them, and the tree updates, or push back in the chat and ask for adjustments.

Open, Sent, Resolved

The panel has three tabs, and a comment moves between them:

Open is what you have written and not sent.
Sent is what the agent has been given.
Resolved is what is settled. Resolving a comment moves it here, and you can reopen it at any time, which sends it back to Open.

Deleting a comment removes it and its replies for good. Resolving is the reversible option; prefer it.

Sync from the codebase

If your project is connected to a repository, the spec tree offers a sync action that pulls the current source of truth back into the specs. It is not refining. Refining proposes changes through the agent; syncing reconciles the spec model with what the codebase actually contains.