Requirement triage and scope gate
When you click Generate Module, OdoMate checks your requirement before it spends any generation budget on it. A quick AI classifier reads what you wrote and decides whether it’s ready to build — and if it isn’t, it stops you before the run starts instead of after.
What triage checks for
Section titled “What triage checks for”The classifier sorts your requirement into one of four categories:
- A new module — new business functionality (new models, views, workflows). Generation starts immediately, no interruption.
- A customization of a native Odoo app — changing, extending, or removing behavior of an existing module (website, sale, hr, account, …), like “remove ‘Powered by Odoo’ from the website footer” or “hide the discount column on invoices.” Generation also starts immediately; OdoMate builds a small addon that inherits from the native module instead of a standalone one.
- Too vague — not enough detail for a developer to build anything from, like “make me an app” or “improve my system.”
- Out of scope — not about Odoo or ERP business software at all.
The first two categories go straight through to generation with no dialog. A short requirement isn’t automatically flagged as too vague — if what you wrote is enough to build from, it’s classified by what it asks for, regardless of length.
When it stops you
Section titled “When it stops you”-
Too vague opens a dialog explaining the request may be too brief to generate a working module, with the classifier’s one-sentence reason underneath. You get two ways forward: Refine first (recommended) sends you into the AI refine chat to add the missing detail, and Generate anyway dismisses the dialog and starts generation with what you already wrote.
-
Out of scope opens a dialog telling you OdoMate builds and customizes Odoo modules, with the same classifier reason underneath. There’s only one way forward here: Edit request closes the dialog and returns you to the requirement text box — there’s no generate-anyway escape hatch for this one.
