wave-planning-optimization

wave-planning-optimization is a skill for Claude Code from kishorkukreja/awesome-supply-chain. It costs 80 tokens per session (7,034 once invoked), scanned A, original, MIT.

A warehouse wave-planning guide for grouping and releasing orders for picking at suitable times.

In plain words
What is it for?
Use it to plan batch-picking waves, release orders, manage priorities, and improve fulfillment timing.
Why use it?
It helps balance picker workload, meet shipping cutoffs, and avoid overloading warehouse equipment or packing stations.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the supply-chain-skills plugin — 133 skills shipped together , and of supply-chain-skills

Good fit Use it to plan batch-picking waves, release orders, manage priorities, and improve fulfillment timing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kishorkukreja/awesome-supply-chain/wave-planning-optimization
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add kishorkukreja/awesome-supply-chain --skill wave-planning-optimization
Clone the repo
git clone --depth 1 https://github.com/kishorkukreja/awesome-supply-chain

Made for: Claude Code.

Or install supply-chain-skills, the plugin that ships this one along with the rest of its 133 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for wave-planning-optimization

README.md
[![agentmods](https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/wave-planning-optimization/github.svg)](https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/wave-planning-optimization)
Your own site
<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/wave-planning-optimization"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/wave-planning-optimization/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for wave-planning-optimization

Your own site · 80×15
<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/wave-planning-optimization"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/wave-planning-optimization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,034 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.07034
Opus 5 $0.00040 $0.03517
Sonnet 5 $0.00016 $0.01407
Haiku 4.5 $0.00008 $0.00703

Measured 9d ago against content hash a84028c2e494, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

wave-planning-optimization scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/wave-planning-optimization/SKILL.md · 943 lines

How it starts

The opening of the file, as written. The whole thing — 943 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Wave Planning Optimization

You are an expert in warehouse wave planning and order release optimization. Your goal is to help design and optimize pick waves to maximize picker productivity, balance workload, meet cutoff times, and improve overall fulfillment efficiency.

Initial Assessment

Before optimizing wave planning, understand:

  1. Operational Characteristics

    • Daily order volume (lines and units)?
    • Order types (each-pick, case-pick, full-pallet)?
    • Warehouse zones and pick methods?
    • Shift structure and available labor?
    • Current wave frequency and size?
  2. Business Requirements

    • Shipping cutoff times?
    • Priority order types (same-day, next-day)?
    • Customer SLAs and promises?
    • Carrier pickup schedules?
    • Order profile (single-line vs. multi-line)?
  3. Constraints

    • Equipment capacity (conveyors, sorters)?
    • Packing station capacity?
    • Shipping dock doors available?
    • Labor availability by shift?
    • WMS capabilities and limitations?
  4. Performance Metrics

    • Current picks per hour?
    • Order cycle time (order → ship)?
    • Labor utilization?
    • On-time shipping performance?
    • Wave completion rates?

Wave Planning Framework

Wave Design Principles

1. Wave Sizing

  • Small Waves (50-200 orders)

    • Pros: Flexible, quick completion, easy re-wave
    • Cons: More frequent releases, higher admin overhead
    • Use: High variability, frequent cutoffs
  • Medium Waves (200-500 orders)

    • Pros: Balanced workload, good equipment utilization
    • Cons: Some idle time between waves
    • Use: Standard operations, moderate volume
  • Large Waves (500-1000+ orders)

    • Pros: Maximum efficiency, fewer releases
    • Cons: Inflexible, longer cycle time
    • Use: High volume, stable demand

2. Wave Frequency

  • Continuous Waves: Release new wave when previous completes
  • Fixed Schedule: Every 2-4 hours (e.g., 8am, 12pm, 4pm)
  • Dynamic: Based on order accumulation threshold
  • Just-in-Time: Aligned with carrier pickups

Read the full file on GitHub · 943 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 943 lines · 80 tokens per session scan A a84028c2e494

Subscribe to this mod's changes

wave-planning-optimization is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 12d ago), licensed MIT. It adds 80 tokens to every session and 7,034 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories