mcpbeat Sign in

Mfg Production Planning Agent Skill

Design production plans using MPS (Master Production Schedule), MRP (Material Requirements Planning), and capacity planning. Use this skill when the user needs to schedule production, plan material procurement, balance capacity with demand, or optimize production sequencing — even if they say 'we can't keep up with orders', 'when should we order materials', 'production scheduling', or 'how do we plan for next quarter's demand'.

9k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill mfg-production-planning

What comes with it

32 774 bytes besides the instruction
examples/sample_scenario.md
references/demand-forecasting.md
references/sop-process.md

The instruction itself

10 sections, as written by the author

Production Planning (MPS/MRP)

Framework

IRON LAW: Plan Hierarchically — Demand → MPS → MRP → Shop Floor

Production planning flows TOP-DOWN:
1. Demand forecast / customer orders → what to make, when
2. MPS → master schedule for finished goods
3. MRP → material and component requirements (what to buy, when)
4. Shop floor scheduling → which machine, which sequence

Skipping levels (going from demand forecast directly to shop floor)
creates chaos — material shortages, capacity conflicts, missed deliveries.

Planning Hierarchy

| Level | Plan | Horizon | Granularity | Decides |

|-------|------|---------|-------------|---------|

| Strategic | S&OP (Sales & Operations Planning) | 12-18 months | Monthly, product family | Capacity investments, workforce planning |

| Tactical | MPS (Master Production Schedule) | 3-6 months | Weekly, end product | What to produce each week |

| Operational | MRP (Material Requirements Planning) | 4-12 weeks | Daily, component/material | What to order, when, how much |

| Execution | Shop Floor Scheduling | 1-2 weeks | Hourly, work center | Sequence, machine assignment |

MPS Process

  • Inputs: Demand forecast + customer orders + current inventory + safety stock targets
  • Logic: For each week, calculate: Production Needed = Demand - Beginning Inventory - Scheduled Receipts + Safety Stock
  • Output: Planned production quantities by week for each finished product
  • Constraint: Must not exceed available capacity (rough-cut capacity planning check)

MRP Process

  • Inputs: MPS (what to make) + BOM (Bill of Materials — what it's made of) + Inventory status + Lead times
  • Logic: "Explode" the BOM — for each finished good, calculate when each component/material must be ordered to arrive in time
  • Output: Planned purchase orders and production orders with dates and quantities
  • Key calculation: Order date = Need date - Lead time

Scheduling Algorithms

| Algorithm | Rule | Best When |

|-----------|------|-----------|

| FCFS (First Come First Served) | Process in order received | Low complexity, fairness matters |

| SPT (Shortest Processing Time) | Shortest job first | Minimize average flow time |

| EDD (Earliest Due Date) | Most urgent due date first | Minimize late deliveries |

| Bottleneck-first | Schedule the constraint first, subordinate rest | Capacity-constrained environments (TOC logic) |

SMED (Single-Minute Exchange of Die)

Reduce changeover time to increase flexibility:

  • Separate internal setup (machine stopped) from external (can do while running)
  • Convert internal to external where possible
  • Streamline remaining internal steps
  • Practice and standardize

Output Format

# Production Plan: {Product/Period}

## Demand vs Capacity
| Week | Demand | Available Capacity | Gap |
|------|--------|-------------------|-----|
| W1 | {units} | {units} | {+/-} |

## Master Production Schedule
| Week | Product A | Product B | Product C | Total |
|------|----------|----------|----------|-------|
| W1 | {units} | {units} | {units} | {units} |

## Material Requirements
| Material | Quantity | Order Date | Supplier | Lead Time |
|----------|---------|-----------|----------|-----------|
| {material} | {qty} | {date} | {supplier} | {days} |

## Scheduling
| Work Center | Mon | Tue | Wed | Thu | Fri |
|------------|-----|-----|-----|-----|-----|
| {center} | {job} | {job} | ... | ... | ... |

Gotchas

  • Forecast accuracy limits everything: MPS/MRP is only as good as the demand forecast. Track forecast accuracy (MAPE) and build safety stock proportional to forecast error.
  • Lead time variability kills plans: If supplier lead time is "2-6 weeks" (4 week variability), you need safety stock for the worst case. Reduce variability through supplier management.
  • BOM accuracy is critical for MRP: A wrong BOM means ordering wrong materials. Audit BOMs quarterly.
  • Frozen zone: The first 1-2 weeks of MPS should be "frozen" (no changes) to allow stable execution. Changes inside the frozen zone cascade chaos through the system.
  • Finite vs infinite capacity: Basic MRP assumes infinite capacity (ignores machine constraints). Always layer a capacity check (rough-cut or detailed) on top of MRP output.

References

  • For S&OP process design, see references/sop-process.md
  • For demand forecasting methods, see references/demand-forecasting.md

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take asgard-ai-platform/mfg-production-planning from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.