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

odoo-mrp

Skill2 starsChanged 3 months agoMITView on GitHub

MANDATORY for Manufacturing Orders (mrp.production), BoMs (mrp.bom), and Work Orders (mrp.workorder). Expertise in Odoo's production engine.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Mandate: When an MO is confirmed, Odoo automatically triggers components reservations and generates Work Orders based on the BoM.

    line 13
  2. Distinctive:

    Mandate: If a BoM is marked as incomplete or part of an ETO flow, the agent should proactively check for additional requirements before …

    line 24
  3. Very specific:

    Engineering Change Orders (ECO): Use mrp.eco to track modifications to BoM structures.

    line 27
  4. Very specific:

    Mandate: All operations must be marked as done before the master MO can be closed.

    line 33

≈ “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 MRP (Manufacturing) & PLM

This skill provides the agent with high-level functional expertise in Odoo's Manufacturing and Product Lifecycle Management (PLM) engines, covering production planning, execution, and engineering changes.

Core Mandates

1. The Production Lifecycle

  • States: draft -> confirmed (Materials reserved) -> progress (Operations started) -> to_close -> done.
  • Mandate: When an MO is confirmed, Odoo automatically triggers components reservations and generates Work Orders based on the BoM.

2. Bills of Materials (BoM)

  • Manufacture: Standard BoM that generates a Manufacturing Order.
  • Kit (Phantom): A bundle of products that are "broken down" into components upon Sales Order delivery (no MO is created).
  • Subcontracting: The BoM triggers a Purchase Order to a vendor who performs the assembly.

3. Dynamic BoMs (ETO & CTO)

Support for complex engineering and configuration scenarios:

  • Configure to Order (CTO): BoM components and operations are dynamically selected based on Product Attributes and Variant Values.
  • Engineer to Order (ETO): MOs that allow for "Incomplete" BoMs, where the agent or technical team adds components and operations on-the-fly during the production process.
  • Mandate: If a BoM is marked as incomplete or part of an ETO flow, the agent should proactively check for additional requirements before closing the MO.

4. Integration with PLM

  • Engineering Change Orders (ECO): Use mrp.eco to track modifications to BoM structures.
  • Versioning: Odoo PLM tracks multiple versions of a BoM. Always verify you are using the active version unless a specific ECO is being implemented.

5. Work Center Execution

  • Work Orders (mrp.workorder): Represent the physical work performed.
  • Tracking: Real duration is logged against mrp.workcenter.
  • Mandate: All operations must be marked as done before the master MO can be closed.

Available Resources

  • mrp-logic.md: Deep-dive into ETO/CTO dynamic BoMs, Subcontracting, and Work Center costing.
  • mrp-fields.json: Dense technical map of fields for Production, BoM, Work Order, and ECO 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