Organize growing intent documents

When documents become repetitive, related topics drift apart, or content needs merging, use Organize Source. The Agent proposes an organization plan for all intent documents, and you decide whether to apply it after reviewing the result.

Save your current edits first. Your intent documents stay unchanged until you accept the plan.

Start organizing

Hover over the intents heading in the sidebar, click the organize button, and confirm. Noea opens an organization chat with progress and an execution trace.

You can first choose an Agent, model, and reasoning effort for Organize Source in Settings → Current Project → Operations.

While it runs, Organized appears in the sidebar with a document tree and change markers. Open a document to preview the draft as it is generated. The preview updates with progress and is not editable.

Review the overall changes

When the run finishes, the organization card shows a summary, change statistics, a character-count comparison, and recommendations. Look at which files are affected and what was merged or moved before reading the text.

The Organized section shows the proposed hierarchy, marking additions, removals, renames, and moves. Click an entry to review it.

The organized draft and current documents are separate views, so you can compare them side by side.

Check proposed deletions

Organization review shows the complete proposed document as read-only text. Content marked for deletion stays in place with a pale red background, strikethrough, and an explanation.

Proposed deletions will be removed by default when you accept. If a requirement still matters, choose Keep. For a whole-file removal, you can choose Keep Entire File. These choices are saved and survive restarting the app.

The bottom navigation steps through proposed deletions across files. List items and table rows remain within their original structure so you can judge them in context.

Compare with the current documents

Choose Compare with Original to open the current document on the other side. If a draft combines several files, select the source to compare.

Check these points in particular:

• Did merging or rewriting lose a condition, such as issuing a reward only once within a streak?
• Were rules for distinct situations mixed together, making their scope unclear?
• Were valid requirements removed? A completed feature is not a reason to delete its intent.
• Is the wording understandable, and does it avoid turning one-time task instructions into lasting requirements?

Organization should improve expression, not silently change requirements. For the difference between removing a constraint and removing a feature, see Write intent that matters.

Accept or reject the whole plan

After reviewing, click Accept. If you chose items to keep, the button shows their count. Acceptance applies to the whole plan, including text and structural changes.

Reject leaves the plan unapplied. You can continue editing the current documents and organize again later.

Accepting a plan that changes document text automatically updates implementation explanations. Changes limited to filenames or folder structure do not trigger Explain. This automatic update is independent of the “Explain automatically after implementing” setting. See Agents, models, and usage for configuration.

Handle an outdated plan

If the current intent changes after a plan was generated, the plan becomes outdated. Acceptance is disabled and Reorganize is offered. Saving a current document during review also warns that it may invalidate the plan.

To rewrite the draft further, reject the plan, edit the current documents, and organize again. Unlike new text in an ordinary proposal, organization-review text cannot be edited directly.

Only one organization plan can await review at a time. Starting another prompts you that the old plan will be discarded.

Next, check whether your explanations need updating.