Extends existing Odoo 16.0 modules with new features, fields, views, business logic, wizards, and reports. This skill should be used when the user requests enhancements to existing functionality, such as "Add a field to track serial numbers in stock.picking" or "Create a wizard for bulk invoice generation" or "Add a report for vendor bill analysis".
View on GitHubJanuary 22, 2026
Select agents to install to:
npx add-skill https://github.com/jamshu/jamshi-marketplace/blob/main/plugins/odoo-dev/skills/odoo-feature-enhancer/SKILL.md -a claude-code --skill odoo-feature-enhancerInstallation paths:
.claude/skills/odoo-feature-enhancer/# Odoo Feature Enhancer ## Overview This skill enables extension of existing Odoo 16.0 modules by adding new fields, views, business logic, wizards, reports, and automated actions. It follows module inheritance patterns and ensures proper integration with existing functionality. ## Enhancement Categories When a user requests a feature enhancement, identify the category and follow the appropriate workflow: ### 1. Field Additions Add new fields to existing models (stored, computed, related). ### 2. View Modifications Extend existing views (tree, form, kanban, calendar, pivot, graph) using XML inheritance. ### 3. Business Logic Add computed methods, onchange handlers, constraints, and custom business rules. ### 4. Wizards Create transient models for user interactions and batch operations. ### 5. Reports Generate PDF (QWeb) or Excel reports with custom data aggregation. ### 6. Server Actions Create automated actions, scheduled actions (cron jobs), and workflow automations. ### 7. Buttons and Actions Add action buttons to forms and tree views. ## Enhancement Workflow ### Step 1: Identify the Enhancement Type Ask clarifying questions based on the request: **For Field Additions:** - Field technical name (snake_case) - Field type (Char, Integer, Float, Boolean, Selection, Many2one, One2many, Many2many, Date, Datetime, Text, Html, Binary, Monetary) - Field label and help text - Required or optional? - Computed field or stored? - Should it appear in specific views? **For View Modifications:** - Which view(s) to modify? (form, tree, search, kanban) - Which model? - Where to add the element? (header, group, notebook page, after specific field) - Any conditional visibility? **For Business Logic:** - Trigger condition (onchange, compute, constraint, button click) - Dependencies (which fields trigger the logic) - Expected behavior **For Wizards:** - Wizard purpose (batch update, data export, configuration, etc.) - Input fields needed - Target models to affect - W