The core workflow07 / 16
Discuss and review intent changes
On this page
When a discussion leads to a new product decision, ask the Agent to turn it into an intent proposal. Review the wording, adjust it if needed, and decide whether to write it into your documents.
Start with specific context
Hover over a relevant paragraph and choose Ask about this on the left. Noea inserts a reference into the input and shows the document beside the chat. It does not send a message automatically.
You can also type @ in the input to search documents, paragraphs, or explanations. Selected content appears as a reference chip and is supplied to the Agent with your message.
For example:
This reward rule does not say what happens after a missed check-in. Explain the current behavior using the implementation, then discuss whether we should allow make-up check-ins.
Once you have decided, ask for a proposal:
Add “Allow one make-up check-in per month” to this rule. Propose the intent change for me to review.
Decide whether to fix code or change the requirement
When intent and implementation disagree, first ask whether the original requirement still stands. Suppose the document requires a reward after 7 consecutive days, but the code issues it on day 6:
| Your decision | Next step |
|---|---|
| The requirement is still 7 days. | Keep the intent. Ask the Agent to fix the implementation and verify the boundary. |
| After discussion, you decide on 6 days. | Change the intent, review the new trigger condition, and check the implementation. |
Do not rewrite intent merely to accommodate existing code. First check that the Agent understood the requirement, then check that the code meets it. Clarify misunderstandings, fix implementation errors, and change intent only when you decide to change the rule.
For a fix, be explicit:
Keep the 7-day requirement. Fix the early reward, verify that day 6 gives no reward and day 7 does, and do not change the intent to fit the current code.
Distinguish suggestions from proposals
A suggestion card records something the Agent thinks is worth adding to intent. Adopt starts work in the current chat to turn it into a proposal that the existing implementation already meets; it does not write directly to your intent. Dismiss records that you are not taking up the suggestion.
A proposal contains specific document changes for you to review. After the Agent submits one, its card appears when the current turn finishes, stops, or fails. Choose View Changes to inspect it.
Review changes in the document
The review view keeps the document's layout. Insertions have a pale green background; deletions have a pale red background and strikethrough. Replacements show old and new text, with word-level changes highlighted where suitable.
Use the bottom review bar to move between changes, or select a filename to switch documents. A decision applies to the entire proposal, including all its files. You cannot accept individual paragraphs or files separately.
You can edit inserted text and the new side of a replacement. Original text, deletions, and unaffected paragraphs cannot be edited in this review state. After editing, the primary action becomes Accept My Edits.
Before deciding, check not only which words changed but what they require:
- Can you explain the added conditions and terms in your own words?
- Has a one-time instruction been mistaken for a lasting requirement?
- Has the Agent quietly weakened a constraint to match existing code?
- Will you be able to find the right sentence next time you want this behavior to change?
If anything is unclear, return to the chat and ask the Agent to explain or revise the proposal.
Choose an action
| Action | Intent document | Implementation |
|---|---|---|
| Accept | Writes the entire proposal. | Continues if work is needed; does not start another run if already satisfied. |
| Accept My Edits | Writes the entire proposal with your edits. | Continues according to the edited proposal. |
| Implement Directly | Does not write the proposal. | Implements it; available only for proposals that still need implementation. |
| Dismiss | Does not apply the proposal. | Does not start its implementation. |
Accept a reviewed decision when you want it to guide future development. Implement Directly does not record this request as intent.
Dismissing a proposal does not undo code changes already made. The Agent may, for example, have completed the work before proposing that you record the existing behavior.
Handle revised proposals and changed documents
The Agent can revise a proposal in the same chat. The new version replaces the pending review, while the older card keeps a version notice. Edits you made but did not accept in the old review are not carried over automatically.
If the current document no longer matches the proposal's starting text, acceptance is disabled. Use Ask Agent to Re-propose on Current Version so the Agent rereads the document and creates changes that can be applied.
After acceptance
A proposal that needs implementation continues in the current chat. If it does not finish, use Continue Implementing on the card. Return to the document afterward and check the explanation; run Explain manually if it did not update.
To stop reviews opening automatically, turn off Settings → Current Project → Automation → Open review automatically, then enter review from the proposal card. This setting controls opening the review, not accepting the proposal.
Continue with Keep explanations up to date.