Plan Odoo workflow skills and metadata

[cbusillo]

Objective

Decide and implement the right Codex/Code support for recurring Odoo work after the Odoo repo/workflow model stabilizes.

Finish Line

Odoo guidance is implemented as focused skills/metadata or intentionally rejected, with no stale local plan left behind.

Current Status

State: Later
Next action: Revisit after current Odoo repo/workspace patterns settle; inventory AGENTS/docs/workflow metadata before creating any new skills.
Blocked by: Odoo workflows, repo ownership, and runtime patterns are still in flux.
Last verified: Migrated from local plan workspace-odoo-skills.md on 2026-05-02.

Scope

• In: Possible Odoo addon workflow skill, devkit workspace workflow, Odoo Intelligence MCP usage guidance, migration/cutover skill, and structured repo workflow metadata.
• Out: Implementing new Odoo skills immediately or freezing volatile guidance globally.

Acceptance Criteria

• Inventory Odoo AGENTS/docs and current workflow metadata.
• Decide which guidance belongs in AGENTS, repo docs, .github/github-repo-workflow.json, or a skill.
• Pilot any Odoo metadata/schema additions in one repo before broad adoption.
• Delete or close this plan when Odoo skills are implemented or intentionally rejected.

Relationships

• None yet.

Validation

• Future skill/metadata changes should be validated on one Odoo repo before broad rollout.

Decisions

• Prefer shared workflow metadata and docs routing over many repo-specific skills where possible.
• Avoid duplicating long Odoo docs into global skills.

Open Questions

• Should Odoo work be driven primarily by workspace roots or source repos?
• Should Odoo Intelligence MCP usage become a global Odoo skill or stay in AGENTS/docs?