agentleFS
Sign inStart free
actinon-comactinon-com/brass-monkey/skills/odoo-plm/SKILL.md

odoo-plm

Skill2 starsChanged 3 months agoMITView on GitHub

High-level functional expertise in Odoo's PLM module, covering Engineering Change Orders, BoM versioning, and change approvals.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Proposed Changes: Instead of modifying a live BoM, use an Engineering Change Order (mrp.eco) to propose modifications.

    line 12
  2. Very specific:

    Mandate: If the PLM module is installed, the agent is strictly forbidden from using write_record to modify an active mrp.bom.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Odoo PLM (Product Lifecycle Management)

This skill provides the agent with high-level functional expertise in Odoo's PLM module, covering Engineering Change Orders (ECO), BoM versioning, and change approvals.

Core Mandates

1. Structure of a Change (ECO)

  • Proposed Changes: Instead of modifying a live BoM, use an Engineering Change Order (mrp.eco) to propose modifications.
  • Types: ECOs are categorized by Type (mrp.eco.type), such as 'BoM Change' or 'Routing Change'.
  • Workflow: ECOs move through Stages (mrp.eco.stage).

2. Prohibited Direct Edits

  • Mandate: If the PLM module is installed, the agent is strictly forbidden from using write_record to modify an active mrp.bom. All changes must be routed through an mrp.eco.

3. Change Tracking

  • BoM Changes (mrp.eco.bom.change): Tracks the addition, removal, or quantity update of components.
  • Routing Changes (mrp.eco.routing.change): Tracks modifications to manufacturing operations or work center assignments.

4. Approvals & Application

  • Approval Flow: Each stage can require one or more approvals. Use search_read on mrp.eco.approval to verify if a change is ready to be applied.
  • Applying Changes: Once approved and moved to the "Apply" stage, Odoo archives the old BoM version and activates the new version created by the ECO.

Available Resources

  • plm-logic.md: Deep-dive into version control, conflict resolution, and effectivity dates.
  • plm-fields.json: Dense technical map of fields for ECO, Type, Stage, and Change models.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free