Menu
Deep investigation of Odoo codebase to understand patterns before proposing solutions. Trigger: /odf-explore, 'how does Odoo handle X', research, investigation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement Odoo tasks from design artifact. Write code following spec + design. Trigger: Phase 3 (IMPLEMENT) of /odf-new after DESIGN approved.
Detect + persist Odoo project context: version, modules, test runner, lint tools, conventions. Trigger: /odf-init, first time in a project.
Quality gate for ODF: evidence-based risk tiers (0/1/4 lenses), spec compliance matrix, single-attempt correction budget. Trigger: Phase 4 (VERIFY) of /odf-new.
Create an ODF change proposal with business context, scope, and approach. Trigger: Phase 0 (PROPOSE) of /odf-new.
Strict TDD mode for ODF: tests before code. Two-source kill switch (global + local), any off wins, fail-closed. Trigger: /odf-tdd on, effective TDD mode active, or when strict TDD enforcement is needed.
Assess Odoo requirement: determine standard vs custom strategy, analyze functional feasibility, produce functional spec. Trigger: Phase 1 (ASSESS) of /odf-new.
| name | odf-explore |
| description | Deep investigation of Odoo codebase to understand patterns before proposing solutions. Trigger: /odf-explore, 'how does Odoo handle X', research, investigation. |
| license | MIT |
| metadata | {"author":"adruban","version":"2.0"} |
Use BEFORE /odf-new when you need to understand how Odoo handles a feature, find existing patterns, or check version differences. Do NOT use for simple questions or bugfixes.
| Rule | Requirement |
|---|---|
| Local source first | ALWAYS search ~/Workspace/Doodba_ENV/O{VER}/odoo/custom/src/odoo/ before concluding |
| Read actual files | Never guess Odoo behavior — read models/, views/, tests/ |
| Standard check | Determine if standard Odoo already covers the need |
| Version noted | APIs change between versions — check the target version specifically |
| Condition | Action |
|---|---|
| Standard Odoo covers the need | Report standard approach + config guide, suggest no custom code |
| Gap exists (partial or full) | Report findings + recommend /odf-new for the missing pieces |
| Unclear how Odoo works | Read local source, check tests for usage patterns, then decide |
Glob and Grep in ~/Workspace/Doodba_ENV/O{VER}/odoo/custom/src/odoo/addons/.Read: __manifest__.py (scope), models/ (logic), views/ (UI), and tests/ (examples).Return exploration report with: status (ok), executive_summary, relevant_modules (table: module, purpose, relevance), key_models (table: model, fields, methods), standard_coverage (Yes/No/Partial), recommendation (start /odf-new or use standard config), artifacts_saved, odoo_version, modules_affected.
/home/adruban/.config/opencode/skills/_shared/result-contract.md — ODF Result envelope/home/adruban/.config/opencode/skills/_shared/odoo-sources.md — Local source paths