odoo-fit-gap
Skill2 starsChanged 14 days agoMITView on GitHub
Classify each Odoo requirement as Standard, Configuration, Studio/Low-code, Customization or Technical Limitation, with justification (why), approach (how), affected modules, effort estimate and workaround. Hosting/edition aware (Community, Enterprise, Odoo.sh, Odoo Online). Use after requirements are clarified and before building a demo or phasing.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Check that the module exists in the edition, e.g.
- Distinctive: line 35
Add standard overheads separately: testing about 20%, project management about 10–15%, and training and data migration as their own lines.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Odoo Fit-Gap Analysis
Categories (use the lowest one that works)
| Code | Category | Definition | Example |
| STD | Standard | Works out of the box once the app is installed | Quotation → Sales Order → Invoice |
| CFG | Configuration | Standard features enabled or set up through settings or master data, no code | Pricelists, multi-step delivery routes, approval rules |
| STU | Studio / Low-code | Enterprise Studio, automation rules, server actions, report tweaks. Enterprise only | Extra field on SO, simple approval automation |
| CUS | Customization | Needs a custom Python/XML/JS module | New business object, complex pricing engine, API integration |
| LIM | Technical Limitation | Not feasible, not advisable, or blocked by edition or hosting | Custom module on Odoo Online; changing core accounting principles |
Edition and hosting rules:
- Community: STU is not available. Re-classify those items as CUS, or CFG if an automation without Studio is possible (
base_automationis in Community). - Odoo Online: every CUS item becomes LIM, unless the client accepts moving to Odoo.sh. Ask the user about this.
- Check that the module exists in the edition, e.g.
account_accountant,mrp_plm,quality,helpdeskandhr_payrollare Enterprise. Verify on the server withodoo_client.py search-read ir.module.module.
For each requirement, record
| REQ | Category | Module(s) | Why (justification) | How (approach) | Effort | Risk | Workaround if LIM | Priority | Phase |
- Why: which standard feature covers it, or why the standard is insufficient (cite the exact menu or behaviour).
- How: the menu path and settings, or for CUS a short technical design (models, fields, views, hooks).
- Effort (estimate only, always shown as a range and labelled indicative):
Size CFG/STU CUS XS < 1 h < 4 h S 1–4 h 0.5–2 d M 0.5–1 d 2–5 d L 1–3 d 5–15 d XL > 3 d > 15 d (split it) Add standard overheads separately: testing about 20%, project management about 10–15%, and training and data migration as their own lines.
Before escalating to CUS, always check
- Is there a standard setting? (Search Settings and the module's configuration menu.)
- Can a process change by the client make the standard version work? Ask the client. Do not decide for them.
- Would a report or filter be enough?
- Is there an Odoo Apps / OCA module? Note it as an option with its licence and maintenance risk. Ask before using it.
Outputs
docs/03_fit_gap_matrix.md(+fit_gap_matrix.csvwith the same columns)docs/04_technical_limitations.md: every LIM item with its reason, its impact and the alternatives offered- A summary: counts per category × priority, and total effort ranges.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- odoo-connectSkill
- odoo-demo-db-builderSkill
- odoo-documentationSkill
- odoo-implementation-workflowSkill
- odoo-project-phasingSkill
- odoo-requirements-analysisSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

