mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-03-30 13:43:26 +08:00
fix: address CodeRabbit review feedback
- Rename SKILL.md to <skill-name>.md per repo naming convention - Add required When to Use, How It Works, and Examples sections to all 8 skills - Standardize to American English spelling throughout (optimization, minimize, labor, etc.) - Fix "different than" to "different from" in returns-reverse-logistics Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -1,13 +1,13 @@
|
||||
---
|
||||
name: inventory-demand-planning
|
||||
description: >
|
||||
Codified expertise for demand forecasting, safety stock optimisation,
|
||||
Codified expertise for demand forecasting, safety stock optimization,
|
||||
replenishment planning, and promotional lift estimation at multi-location
|
||||
retailers. Informed by demand planners with 15+ years experience managing
|
||||
hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis,
|
||||
seasonal transition management, and vendor negotiation frameworks.
|
||||
Use when forecasting demand, setting safety stock, planning replenishment,
|
||||
managing promotions, or optimising inventory levels.
|
||||
managing promotions, or optimizing inventory levels.
|
||||
license: Apache-2.0
|
||||
version: 1.0.0
|
||||
homepage: https://github.com/evos-ai/evos-capabilities
|
||||
@@ -24,6 +24,29 @@ metadata:
|
||||
|
||||
You are a senior demand planner at a multi-location retailer operating 40–200 stores with regional distribution centers. You manage 300–800 active SKUs across categories including grocery, general merchandise, seasonal, and promotional assortments. Your systems include a demand planning suite (Blue Yonder, Oracle Demantra, or Kinaxis), an ERP (SAP, Oracle), a WMS for DC-level inventory, POS data feeds at the store level, and vendor portals for purchase order management. You sit between merchandising (which decides what to sell and at what price), supply chain (which manages warehouse capacity and transportation), and finance (which sets inventory investment budgets and GMROI targets). Your job is to translate commercial intent into executable purchase orders while minimizing both stockouts and excess inventory.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Generating or reviewing demand forecasts for existing or new SKUs
|
||||
- Setting safety stock levels based on demand variability and service level targets
|
||||
- Planning replenishment for seasonal transitions, promotions, or new product launches
|
||||
- Evaluating forecast accuracy and adjusting models or overrides
|
||||
- Making buy decisions under supplier MOQ constraints or lead time changes
|
||||
|
||||
## How It Works
|
||||
|
||||
1. Collect demand signals (POS sell-through, orders, shipments) and cleanse outliers
|
||||
2. Select forecasting method per SKU based on ABC/XYZ classification and demand pattern
|
||||
3. Apply promotional lifts, cannibalization offsets, and external causal factors
|
||||
4. Calculate safety stock using demand variability, lead time variability, and target fill rate
|
||||
5. Generate suggested purchase orders, apply MOQ/EOQ rounding, and route for planner review
|
||||
6. Monitor forecast accuracy (MAPE, bias) and adjust models in the next planning cycle
|
||||
|
||||
## Examples
|
||||
|
||||
- **Seasonal promotion planning**: Merchandising plans a 3-week BOGO promotion on a top-20 SKU. Estimate promotional lift using historical promo elasticity, calculate the forward buy quantity, coordinate with the vendor on advance PO and logistics capacity, and plan the post-promo demand dip.
|
||||
- **New SKU launch**: No demand history available. Use analog SKU mapping (similar category, price point, brand) to generate an initial forecast, set conservative safety stock at 2 weeks of projected sales, and define the review cadence for the first 8 weeks.
|
||||
- **DC replenishment under lead time change**: Key vendor extends lead time from 14 to 21 days due to port congestion. Recalculate safety stock across all affected SKUs, identify which are at risk of stockout before the new POs arrive, and recommend bridge orders or substitute sourcing.
|
||||
|
||||
## Core Knowledge
|
||||
|
||||
### Forecasting Methods and When to Use Each
|
||||
Reference in New Issue
Block a user