Odoo module scaffold

A module installs only when its declared structure matches what the registry expects: every Python file imported, every data file listed in __manifest__.py, and listed in dependency order. A model file you forgot to import, or a security file loaded after the view that needs its group, fails — sometimes loudly, often silently (the element just never appears).

Version floor: Odoo 17/18, through Odoo 19 (current LTS). Layout/manifest below is current; pre-17 deltas → skills/odoo-introspect/references/version-matrix.md.

depends decides your MRO layer — introspect first

depends is the one manifest key with weight beyond "make it install": it sets module load order, which sets where your class lands in the model's MRO. Override sale.order while depending only on sale (not sale_stock) and your method sits at a different layer than the stock hooks — super() then reaches a different chain than you expect.

Before writing depends, run the odoo-introspect skill's model_brief (Layer A) on the model you extend: it reports the recommended manifest depends for the fields/methods you touch. Add only what you use. (→ odoo-dev for the override itself.)

Standard layout