本文へ移動
cccskills
無料GitHub で公開

inventory-reorder-planner

Turn sales history and current stock counts into reorder points, order quantities, and a this-week purchase list -- so a product business stops stocking out of winners and stops burying cash in losers. Handles seasonality, supplier lead times, and the dead-stock cleanup.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Inventory Reorder Planner

Stockouts burn revenue on the products that sell; overstock buries cash in the ones that do not. Both come from ordering by gut. Input: sales history export (POS, Shopify, marketplace, or spreadsheet), current stock counts, and supplier lead times (asked per supplier if not provided). Output: reorder points per SKU and the purchase list for this week.

Workflow

  1. Profile every SKU. From sales history: average daily/weekly velocity, variability, trend (growing/flat/dying), and seasonality where the history is long enough to show it (holiday spikes, summer lulls) -- flagged per SKU, never assumed.
  2. Classify. ABC by revenue contribution (A: the ~20% of SKUs driving ~80%), crossed with velocity: WINNERS (high velocity, healthy margin -- never stock out), STEADY, SLOW, DEAD (no sales in 90+ days with stock on hand).
  3. Compute reorder points. Per SKU: lead-time demand (velocity x supplier lead time) plus safety stock scaled to demand variability and the SKU's class -- A items get generous buffers, C items get lean ones. Show the formula inputs per SKU so the owner can sanity-check against what they know ("velocity 4/wk, lead time 3 wks, safety 1.5 wks = reorder at 18").
  4. The purchase list. reorder-plan.csv: every SKU at or below reorder point, recommended order quantity (covering the review cycle plus lead time, respecting supplier minimums and case packs when known), cost, and supplier -- grouped by supplier to build actual POs. Flag URGENT where projected stockout lands before the order can arrive.
  5. Free the cash. The dead-stock report: units, cost tied up, days since last sale, and the exit per item -- bundle with a winner, discount, donate for the writeoff, or return to supplier. Cash sitting in dead stock is the cheapest funding most product businesses never tap.

Rules

  • Velocity from real sales only; no history means NEW -- judgment order, clearly separated from computed recommendations.
  • Stockout periods bias velocity down -- when the data shows zero-stock stretches, compute velocity from in-stock days only and note it.
  • Seasonality is applied only where the data shows it, and the applied multiplier is stated per SKU.
  • Supplier constraints (minimums, case packs, price breaks) are asked for, and rounding to meet them is shown, not silent.
  • A items err toward buffer, C items err toward lean -- one safety-stock policy for everything is the amateur tell.
  • Re-run on a cadence (weekly or per supplier order cycle); each run compares last cycle's recommendation to what actually sold and tightens.

Quick Commands

  • "Plan from [sales export] and [stock counts]" -- full workflow
  • "What do I order this week?" -- the purchase list only
  • "What's about to stock out?" -- URGENT list
  • "Where's my cash buried?" -- dead-stock report

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3392026年10月2日 更新

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3392026年10月2日 更新

Use to test whether an AI agent, prompt, or skill actually works before or after it ships — build a small eval set, score runs, and catch regressions when the prompt or model changes. Trigger when the user asks whether a prompt is good, wants to compare models or versions, sees inconsistent agent output, or is about to put an agent in front of customers.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3392026年10月2日 更新

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3392026年10月2日 更新

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3392026年10月2日 更新

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

日本語の概要は準備中です。原文の説明を表示しています。

OneWave-AI/claude-skills3392026年10月2日 更新

OneWave-AI のスキルをすべて見る

このスキルの問題を報告する