Develop Custom Odoo Modules

This skill turns an AI into an expert Odoo custom module developer, guiding module scaffolding, model definition, security setup, and adherence to Odoo's coding conventions for both Community and Enterprise editions. Activated by mentioning @odoo-module-developer and describing the module, it generates a full folder structure (__manifest__.py, __init__.py, models/, views/, security/, data/), and can also review pasted existing code against Odoo best practices. Its worked example scaffolds a "hospital_management" module with a hospital.patient model: a __manifest__.py declaring name, version 17.0.1.0.0, category, dependencies on base and mail, data files, and an LGPL-3 license, plus a model file inheriting mail.thread and mail.activity.mixin with name, birth_date, doctor_id, and a state selection field.

Use it when starting a new custom Odoo module from scratch, extending an existing Odoo model such as adding fields to sale.order, troubleshooting module loading errors or manifest issues, or implementing onchange, compute, and constraint methods correctly. It does not cover OWL JavaScript components or frontend widget development (use @odoo-xml-views-builder instead), does not generate automated test files (use @odoo-automated-tests), does not cover multi-company or multi-website configuration, and targets Odoo v14+ since Odoo 13 and below use a different module structure without __manifest__.py auto-loading.

Input is a natural-language description of the module to build, or existing module code to review; output is a scaffolded module tree with manifest, models, views, and security files, or a best-practices review of pasted code. The example manifest shows the expected shape:

{
    'name': 'Hospital Management',
    'version': '17.0.1.0.0',
    'category': 'Healthcare',
    'depends': ['base', 'mail'],
    'data': [
        'security/ir.model.access.csv',
        'views/hospital_patient_views.xml',
    ],
    'installable': True,
    'license': 'LGPL-3',
}

Built specifically for Odoo's module system and ORM (odoo.models, odoo.fields, odoo.api), and chains with two sibling skills: @odoo-xml-views-builder for view XML and frontend work, and @odoo-automated-tests for test generation.

Developers building or maintaining custom Odoo modules who want scaffolding and code review that follows Odoo conventions, such as namespaced model names, _inherit instead of modifying core files, correct manifest versioning, and a populated ir.model.access.csv, rather than assembling module structure from scratch each time. The skill's best-practices checklist spells out both directions: always prefix a model's _name with a namespace, use _inherit = ['mail.thread'] to get chatter and logging automatically, format version as {odoo_version}.{major}.{minor}.{patch}, and set 'author' and 'website' in the manifest so the module is identifiable in the Apps list; conversely, never modify core Odoo model files directly, never forget to register new models in ir.model.access.csv (or users hit access errors), and never use spaces or uppercase letters in folder names, since Odoo requires snake_case module names.