AGENT SKILL

odoo-manufacturing-advisor

Expert guide for Odoo Manufacturing: Bills of Materials (BoM), Work Centers, routings, MRP planning, and production order workflows.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
odoo-manufacturing-advisor
risk
safe
source
self
description
Expert guide for Odoo Manufacturing: Bills of Materials (BoM), Work Centers, routings, MRP planning, and production order workflows.

03 SKILL.md 正文

Odoo Manufacturing Advisor

Overview

This skill helps you configure and optimize Odoo Manufacturing (MRP). It covers Bills of Materials (BoM), Work Centers, routing operations, production order lifecycle, and Material Requirements Planning (MRP) runs to ensure you never run short of materials.

When to Use This Skill

  • Creating or structuring Bills of Materials for finished goods.
  • Setting up Work Centers with capacity and efficiency settings.
  • Running an MRP to automatically generate purchase and production orders from demand.
  • Troubleshooting production order discrepancies or component availability issues.

How It Works

  1. Activate: Mention @odoo-manufacturing-advisor and describe your manufacturing scenario.
  2. Configure: Receive step-by-step instructions for BoM setup, routing, and MRP configuration.
  3. Plan: Get guidance on running MRP and interpreting procurement messages.

Examples

Example 1: Create a Bill of Materials

Menu: Manufacturing → Products → Bills of Materials → New

Product: Finished Widget v2
BoM Type: Manufacture This Product
Quantity: 1 (produce 1 unit per BoM)

Components Tab:
  - Raw Plastic Sheet  | Qty: 0.5  | Unit: kg
  - Steel Bolt M6      | Qty: 4    | Unit: Units
  - Rubber Gasket      | Qty: 1    | Unit: Units

Operations Tab (requires "Work Orders" enabled in MFG Settings):
  - Operation: Injection Molding | Work Center: Press A   | Duration: 30 min
  - Operation: Assembly          | Work Center: Line 1    | Duration: 15 min

BoM Types explained:

  • Manufacture This Product — standard production BoM, creates a Manufacturing Order
  • Kit — sold as a bundle; components are delivered separately (no MO created)
  • Subcontracting — components are sent to a subcontractor who returns the finished product

Example 2: Configure a Work Center

Menu: Manufacturing → Configuration → Work Centers → New

Work Center: CNC Machine 1
Working Hours: Standard 40h/week
Time Efficiency: 85%      (machine downtime factored in; 85% = 34 effective hrs/week)
Capacity: 2               (can run 2 production operations simultaneously)
OEE Target: 90%           (Overall Equipment Effectiveness KPI target)
Costs per Hour: $75.00    (used for manufacturing cost reporting)

Example 3: Run the MRP Scheduler

The MRP scheduler runs automatically via a daily cron job.
To trigger it manually:

Menu: Inventory → Operations → Replenishment → Run Scheduler
(or Manufacturing → Planning → Replenishment in some versions)

After running, review procurement exceptions:
Menu: Inventory → Operations → Replenishment

Message Types:
  "Replenish"   — Stock is below minimum; needs a PO or MO
  "Reschedule"  — An order's scheduled date conflicts with demand
  "Cancel"      — Demand no longer exists; the order can be cancelled

Best Practices

  • ✅ Do: Enable Work Orders in Manufacturing Settings to use routing and time-tracking per operation.
  • ✅ Do: Use BoM with variants (via product attributes) for products that come in multiple configurations (color, size, voltage) — avoids duplicate BoMs.
  • ✅ Do: Set Lead Times on components (vendor lead time + security lead time) so MRP schedules purchase orders in advance.
  • ✅ Do: Use Scrap Orders when discarding defective components during production — never adjust stock manually.
  • ❌ Don't: Manually create purchase orders for MRP-managed items — override MRP suggestions only when justified.
  • ❌ Don't: Confuse Kit BoM with Manufacture This Product — a Kit never creates a Manufacturing Order.

Limitations

  • This skill targets Odoo Manufacturing (mrp) module. Maintenance, PLM (Product Lifecycle Management), and Quality modules are separate Enterprise modules not covered here.
  • Subcontracting workflows (sending components to a third-party manufacturer) have additional receipt and valuation steps not fully detailed here.
  • Lot/serial number traceability in production (tracking which lot was consumed per MO) adds complexity; test with small batches before full rollout.
  • MRP calculations assume demand comes from Sale Orders and Reordering Rules — forecasts from external systems require custom integration.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1