agentleFS
teodstrteodstr/boardroom/skills/supply-chain-strategy/SKILL.md

supply-chain-strategy

Skill0 starsChanged 3 days agoMITView on GitHub

Choose the right supply chain for a product, efficient (lean) or responsive (agile), using Fisher's product–supply chain match and Lee's uncertainty framework, then derive decisions on sourcing, inventory, production and distribution. Use for operations strategy, supply chain redesign, "lean vs agile" questions and logistics case studies. Triggers: "supply chain strategy", "lean vs agile", "responsive supply chain", "Fisher model", "stratégie supply chain", "chaîne logistique", "chaîne d'approvisionnement", "lean ou agile", "estrategia de cadena de suministro", "cadena de suministro ágil".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No invented figures: label estimates as assumptions.

    line 78

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

Supply chain strategy

Match the supply chain to the uncertainty of the product's demand and supply, then turn that choice into concrete decisions and indicators.

When to use

  • "Should our supply chain be lean or agile?", stockouts and markdowns at the same time, rising logistics costs, supply chain case studies.
  • For the business model as a whole, use business-model-canvas.

Inputs

  1. The product(s): demand pattern, life cycle, margins, variety, forecast accuracy.
  2. The supply side: suppliers, locations, lead times, process maturity, risks.
  3. Current problems and indicators: stockouts, inventory levels, costs, lead times.

Method

  1. Characterize demand (Fisher):
    • Functional products: stable, predictable demand, long life cycles, low margins, little variety (staple foods, basic clothing, consumables).
    • Innovative products: unpredictable demand, short life cycles, high margins, high variety (fashion, consumer electronics).
  2. Characterize supply (Lee): stable (mature processes, reliable suppliers) or evolving (new processes, few suppliers, quality or capacity risks).
  3. Match the strategy using the grid below.
Stable supplyEvolving supply
Functional productEfficient (lean): lowest cost, high utilization, low inventoryRisk-hedging: pooled inventory, several suppliers
Innovative productResponsive: speed, flexibility, spare capacity, build to orderAgile: responsive and risk-hedging combined
  1. Diagnose mismatches. An innovative product run through an efficient chain causes stockouts and markdowns. A functional product run through a responsive chain wastes money.
  2. Combine where useful: lean upstream and agile downstream, separated by a decoupling point, with postponement (finishing the product as late as possible, once demand is known).
  3. Derive the decisions: sourcing (one or several suppliers, nearshore or offshore), inventory (where, how much safety stock), production (make to stock, assemble to order, make to order), distribution (central or local warehouses), information sharing with partners.
  4. Pick the indicators: cost to serve, on-time in-full (OTIF), fill rate, inventory turnover, lead time, forecast accuracy, markdowns.

Output

### Diagnosis — <product>
| Criterion | Observation | Reading |
|---|---|---|
| Demand predictability | … | Functional / innovative |
| Supply stability | … | Stable / evolving |

### Recommended strategy
<Efficient, risk-hedging, responsive or agile, and why.>

### Decisions
| Lever | Today | Target | Why |
|---|---|---|---|
| Sourcing | … | … | … |
| Inventory | … | … | … |
| Production | … | … | … |
| Distribution | … | … | … |

### Indicators
| Indicator | Today | Target |
|---|---|---|

Quality bar

  • The product is classified with evidence (demand variability, life cycle, margins), not intuition.
  • Supply uncertainty is assessed separately from demand uncertainty.
  • Mismatches are explained by their symptoms (stockouts, markdowns, excess cost).
  • Decisions are concrete, linked to the chosen strategy, and come with indicators.
  • No invented figures: label estimates as assumptions.
  • Written in the user's language, with the standard terms below.

Terminology

EnglishFrançaisEspañol
Supply chainChaîne logistique (supply chain)Cadena de suministro
Efficient / responsive supply chainSupply chain efficiente / réactiveCadena de suministro eficiente / de respuesta rápida
Lead timeDélai d'approvisionnementPlazo de entrega
Safety stockStock de sécuritéStock de seguridad
PostponementDifférenciation retardéePostergación
Make to stock / make to orderProduction sur stock / à la commandeFabricación contra stock / bajo pedido
Decoupling pointPoint de découplagePunto de desacoplamiento

Sources

  • Fisher, M. L. (1997). What is the right supply chain for your product? Harvard Business Review, 75(2), 105–116.
  • Lee, H. L. (2002). Aligning supply chain strategies with product uncertainties. California Management Review, 44(3), 105–119.
  • Christopher, M. (2000). The agile supply chain: Competing in volatile markets. Industrial Marketing Management, 29(1), 37–44.

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.