@rubix0270/arboris 1.0.1 → 1.0.3

package/prisma/skills/intent-driven-development/SKILL.md

@@ -1,360 +0,0 @@
----
-name: intent-driven-development
-description: Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
----
-
-# Intent-Driven Development
-
-Produce useful acceptance criteria without turning specification into ceremony. Inspect
-available context first, expose genuine ambiguity, and choose verification methods that fit
-the work and its risk.
-
-## When to Activate
-
-- User asks to clarify a feature, define acceptance criteria, or de-risk a change before implementation
-- Request touches security, authentication, persistent data, migrations, external APIs, or compliance
-- User wants to prepare a handoff artifact for another agent or team
-- Request is ambiguous enough that the expected outcome is not yet observable or testable
-- User explicitly invokes this skill with `/intent-driven-development`
-
-Do not activate for trivial edits, straightforward one-line fixes, active debugging sessions,
-code review requests, or implementation requests whose acceptance conditions are already clear.
-
-## How It Works
-
-1. **Inspect context first** — reads the repository, docs, schemas, and test infrastructure for technical facts before asking any question, while treating product/business constraints as something only the user or a product artifact can supply
-2. **Choose depth** — selects Quick Capture (3-7 criteria, low/moderate risk) or Full Acceptance Brief (security, data, migration, cross-system changes) based on the risk profile
-3. **Ask minimally** — only asks questions whose answers cannot be inferred and that materially change scope or behavior
-4. **Write observable criteria** — each AC-NNN describes a starting condition, trigger, expected outcome, prohibited side effect, verification method, and priority; no vague words like "correctly" or "securely" without evidence
-5. **Proceed or hand off** — for clear requests with no blocking risks, records criteria and continues; for risky changes, presents blockers and waits for confirmation
-6. **Handle revision** — if an AC fails mid-implementation due to architectural constraints, marks it `[revised]`, updates scope or verification method, increments the revision number, and re-presents only the changed criteria
-
-## Examples
-
-**Quick Capture — "Add CSV export to the dashboard"**
-
-```
-Goal: Authenticated users can download dashboard data as a CSV file.
-In scope: Export of currently filtered rows; filename includes date.
-Out of scope: Scheduled exports, email delivery, Excel format.
-Assumptions: Max row count is under 10k; no PII in exported fields.
-
-AC-001: Export generates file with correct headers
-- Scenario: authenticated user, at least one data row visible
-- Action: click "Export CSV"
-- Expected: browser downloads file with columns [id, name, created_at]
-- Must not: expose internal fields or rows belonging to other users
-- Verification: automated integration test + manual schema spot-check
-- Priority: Required
-```
-
-**Full Acceptance Brief trigger — "Migrate user auth to OAuth"**
-
-Auth change + external dependency + existing session data → Full Brief with Risk Review table,
-blocking decisions on session invalidation strategy, and explicit rollback AC.
-
-**Existing spec review — user pastes a PRD**
-
-Skill reviews it for missing scope boundaries, unverifiable requirements ("the system shall be fast"),
-and silent assumptions, then returns corrected or supplemental criteria without restarting discovery.
-
-## Operating Rules
-
-1. Inspect the available repository, documentation, issue, design, and test context before
-   asking for technical facts that can be discovered locally.
-2. Do not infer product or business constraints from code. Business rules, compliance and
-   regulatory obligations, contractual SLAs, pricing, data-retention policy, prioritization,
-   and target users cannot be read from a repository. Treat them as unknown until the user
-   supplies them or an authoritative product artifact (PRD, contract, policy document) states
-   them. Record them as assumptions flagged for confirmation, never as discovered facts. The
-   repository tells you how the system behaves today, not what the business requires it to do.
-3. Ask only questions whose answers are required and cannot be safely inferred. Group short,
-   related questions when that saves unnecessary turns.
-4. Do not block implementation by default. When the user has asked to implement a sufficiently
-   clear change, record key assumptions and acceptance criteria briefly, then proceed or hand
-   them to the implementation workflow.
-5. Require explicit user confirmation before proceeding only when an unresolved decision could
-   create material security exposure, data loss, irreversible migration, contractual/API
-   breakage, meaningful cost, or destructive external action.
-6. Do not write an acceptance document into a repository, alter project files, create a branch,
-   commit, or invoke another skill unless the user requests it or the active repository
-   workflow explicitly requires it.
-7. Treat automated tests as evidence, not truth. Prefer automation when reliable and
-   proportionate; allow manual UX, accessibility, security, legal, or operational verification
-   where automation cannot establish the outcome.
-8. Never include real secrets, credentials, tokens, private keys, personal data, or sensitive
-   production payloads in acceptance criteria, fixtures, examples, or saved artifacts. Use
-   redacted or synthetic values.
-9. Do not run destructive tests, migrations, security probes, load tests, paid external calls,
-   or operations against production/live data without explicit authorization and an identified
-   safe environment.
-10. When an acceptance criterion cannot be satisfied due to an architectural, platform, or
-   external constraint discovered during implementation, do not silently drop or workaround it.
-   Update the affected criterion (mark it `[revised]`, state the constraint, and adjust scope or
-   verification method), increment the revision number, and re-present only the changed criteria
-   to the user before continuing. Require explicit confirmation only if the revision changes a
-   blocking decision or materially reduces safety or correctness guarantees.
-
-## Choose The Depth
-
-Use the smallest useful output.
-
-### Quick Capture
-
-Use for a clear but non-trivial change with low or moderate risk. Produce:
-
-- Goal
-- In scope / out of scope
-- Assumptions
-- 3-7 acceptance criteria with verification methods
-- Blocking questions, if any
-
-Do not delay implementation for approval unless a blocking risk from the operating rules
-exists or the user specifically asked for a specification first.
-
-### Full Acceptance Brief
-
-Use for ambiguous, cross-system, security-sensitive, data-changing, migration, compliance,
-or high-cost changes, or when the user requests a handoff artifact. Produce the full template
-below and request confirmation for unresolved blocking decisions before risky implementation.
-
-### Existing Specification Review
-
-When the user already supplied a PRD, issue, plan, or acceptance criteria:
-
-1. Review it instead of restarting discovery.
-2. Identify missing scope boundaries, unsafe assumptions, contradictions, and unverifiable
-   requirements.
-3. Return corrected or supplemental criteria.
-
-## Workflow
-
-### 1. Establish Goal And Risk
-
-Extract or ask for:
-
-- The observable outcome for the user or system.
-- The actors affected.
-- The main failure consequence.
-- Risk dimensions that actually apply: security/privacy, persistent data, compatibility/API,
-  migration, external dependencies, cost, concurrency, performance, usability/accessibility.
-
-Avoid asking generic questions about irrelevant risks.
-
-### 2. Discover Context
-
-When local or connected artifacts are available, inspect only what is needed:
-
-- Existing behavior and directly related files or interfaces.
-- Repository conventions, product docs, API contracts, data schemas, or migration history.
-- Existing verification infrastructure and realistic commands.
-- External dependencies and whether they are testable in isolation.
-
-Record discovered facts separately from user-provided assumptions. If context cannot be
-inspected, say what is unknown and ask focused questions.
-
-The repository reveals technical facts — how the system behaves today, its conventions, and
-its contracts. It does not reveal product or business constraints: business rules, compliance
-and regulatory obligations, contractual SLAs, pricing, data-retention policy, prioritization,
-and target users. Never reconstruct these from code or naming. Capture them only from the user
-or an authoritative product artifact, and list them as assumptions to confirm until then.
-
-### 3. Define Scope
-
-State:
-
-- Goal: one sentence describing the intended outcome.
-- In scope: behavior this change must deliver.
-- Out of scope: tempting adjacent work explicitly excluded.
-- Assumptions: claims not yet proven.
-- Blocking decisions: unresolved choices that materially affect safety or behavior.
-
-### 4. Write Acceptance Criteria
-
-Use `AC-001`, `AC-002`, and so on. Each criterion must describe observable behavior and an
-appropriate verification method; criteria and tests are not required to map one-to-one.
-
-For each applicable criterion include:
-
-- Scenario or starting condition.
-- Action or trigger.
-- Expected observable behavior.
-- Prohibited side effect when meaningful.
-- Verification method: automated test, integration check, manual UX review, accessibility
-  check, security review, operational check, or stakeholder acceptance.
-- Environment/safety constraint when verification could affect data, services, cost, or secrets.
-- Priority: required, important, or optional.
-
-Do not use words such as "correctly", "securely", "fast", "intuitive", or "robust" without
-defining observable evidence or recording them as a human-review judgment.
-
-### 5. Cover Only Relevant Boundaries
-
-Consider these categories, but include only categories that apply:
-
-| Category | Include when | Typical evidence |
-| --- | --- | --- |
-| Happy path | New or changed user-visible behavior | Successful workflow or state transition |
-| Validation | The change accepts input | Rejected malformed or boundary value without mutation |
-| Authorization/privacy | Data or actions have access boundaries | Denied access and no sensitive disclosure |
-| Persistence/migration | Stored data or schemas change | Backward read, migration, rollback or backup behavior |
-| Compatibility | Public APIs, files, events, or clients may break | Existing contract or fixture remains valid |
-| Failure recovery | Network, service, or asynchronous failure exists | No partial state or clear retry/degraded behavior |
-| Idempotency/concurrency | Repeats or simultaneous writes are plausible | No duplicate side effect or invalid final state |
-| Performance | A user or service threshold matters | Defined measurement conditions and threshold |
-| UX/accessibility | A person interacts with the result | Keyboard, feedback, error recovery, visual/manual review |
-
-### 6. Present And Continue
-
-- For a clarification/specification request, present the brief and ask for decisions only on
-  listed blockers.
-- For an implementation request with no blocker, present a compact criteria summary as part of
-  the work and continue with implementation.
-- For handoff to another agent or team, include enough context and verification detail for them
-  to act without inventing requirements.
-- Save the brief to a file only when requested. Use a repository-approved path when one exists;
-  otherwise ask for or state the chosen destination before writing.
-
-## Output Template
-
-Use this template for a Full Acceptance Brief. Omit irrelevant sections for Quick Capture.
-
-```markdown
-# Acceptance Brief: <Change Name>
-
-**Status:** Draft | Approved | Implemented | Verified
-**Revision:** <number>
-**Prepared for:** <user/team/agent, when known>
-**Approval required before risky work:** Yes | No - <reason>
-
-## Revision Log
-
-| Rev | Date | Changed criteria | Reason |
-| --- | --- | --- | --- |
-| 1 | <date> | — | Initial draft |
-
-## Goal
-
-<One observable outcome sentence.>
-
-## Scope
-
-**In scope**
-- <behavior included>
-
-**Out of scope**
-- <adjacent work excluded>
-
-## Context
-
-**Discovered facts** (technical, verified from repository or artifact)
-- <how the system behaves today, conventions, contracts>
-
-**Product/business constraints** (supplied by user or product artifact, never inferred from code)
-- <business rule, compliance/SLA obligation, retention policy, priority, target user — or "none supplied yet">
-
-**Assumptions**
-- <unverified claim to confirm or validate>
-
-**Dependencies and constraints**
-- <external service, local convention, compatibility obligation, environment limit>
-
-## Risk Review
-
-| Risk area | Applies? | Required handling |
-| --- | --- | --- |
-| Security/privacy | Yes/No | <redaction, authorization, review, etc.> |
-| Persistent data/migration | Yes/No | <compatibility, backup, rollback, etc.> |
-| External effects/cost | Yes/No | <sandbox/test environment/authorization> |
-| Compatibility/API | Yes/No | <contract to preserve or version> |
-| UX/accessibility | Yes/No | <manual or automated evidence> |
-
-## Acceptance Criteria
-
-### AC-001: <observable behavior>
-- **Scenario:** <starting condition>
-- **Action:** <single trigger>
-- **Expected:** <observable result>
-- **Must not:** <prohibited side effect, if applicable>
-- **Verification:** <method and intended evidence>
-- **Environment/safety:** <constraints, if applicable>
-- **Priority:** Required | Important | Optional
-
-## Blocking Decisions
-
-- [ ] <only decisions that prevent safe or correct progress>
-
-## Verification Plan
-
-| Criterion | Verification evidence | Status |
-| --- | --- | --- |
-| AC-001 | <test/check/review command or evidence type> | Pending |
-```
-
-## Pass/Fail Examples
-
-Use these to judge whether the skill actually produced a verifiable brief, not planning prose.
-
-**A failing acceptance criterion**
-
-```
-AC-001: The export works correctly and is secure.
-```
-
-Fails — "works correctly" and "secure" are not observable, there is no scenario, trigger,
-expected result, or verification method, and nothing states what must not happen. A reader
-cannot tell whether the implementation satisfied it.
-
-**A passing acceptance criterion**
-
-```
-AC-001: Export generates file with correct headers
-- Scenario: authenticated user, at least one data row visible
-- Action: click "Export CSV"
-- Expected: browser downloads file with columns [id, name, created_at]
-- Must not: expose internal fields or rows belonging to other users
-- Verification: automated integration test + manual schema spot-check
-- Priority: Required
-```
-
-Passes — a concrete observable outcome, a prohibited side effect, and a named verification
-method. Two people would agree on whether it was met.
-
-**A failing context entry**
-
-```
-Discovered facts: Users on the free tier are limited to 100 exports per month.
-```
-
-Fails — a per-tier limit is a business rule. It must not appear under discovered facts inferred
-from code; it belongs under Product/business constraints, supplied by the user, or be listed as
-an assumption to confirm.
-
-### Pass/Fail Rubric
-
-A brief passes only if every answer is "yes". Any "no" means revise before returning it.
-
-- [ ] Does every required criterion have a scenario, an observable expected result, and a named verification method?
-- [ ] Are all vague terms ("correctly", "secure", "fast", "robust") either replaced with observable evidence or marked as human judgment?
-- [ ] Are product/business constraints listed as supplied/assumed, with none silently inferred from code?
-- [ ] Is scope explicit, with out-of-scope items named?
-- [ ] Are blocking decisions limited to choices that actually affect safety or correctness, not preferences?
-
-## Quality Check
-
-Before returning the brief, check:
-
-- The goal describes an outcome rather than an implementation choice.
-- Scope boundaries and assumptions are explicit.
-- Every required criterion is observable or clearly marked for human judgment.
-- Security, privacy, data, compatibility, external-effect, and UX risks were considered only
-  where relevant and not silently ignored.
-- Verification methods identify safe environments for risky operations.
-- No secret or production-sensitive information was copied into the output.
-- No repository mutation or implementation block is imposed without justification or request.
-
-## Handoff
-
-When another planning or implementation workflow is available, pass the acceptance brief or
-criterion IDs to it. When no dedicated workflow exists, provide the brief directly as the
-implementation reference. Do not assume any named skill or tool is installed.

package/prisma/skills/inventory-demand-planning/SKILL.md

@@ -1,247 +0,0 @@
----
-name: inventory-demand-planning
-description: >
-  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 optimizing inventory levels.
-license: Apache-2.0
-version: 1.0.0
-homepage: https://github.com/affaan-m/everything-claude-code
-metadata:
-  origin: ECC
-  author: evos
-  clawdbot:
-    emoji: ""
----
-
-# Inventory Demand Planning
-
-## Role and Context
-
-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
-
-**Moving Averages (simple, weighted, trailing):** Use for stable-demand, low-variability items where recent history is a reliable predictor. A 4-week simple moving average works for commodity staples. Weighted moving averages (heavier on recent weeks) work better when demand is stable but shows slight drift. Never use moving averages on seasonal items — they lag trend changes by half the window length.
-
-**Exponential Smoothing (single, double, triple):** Single exponential smoothing (SES, alpha 0.1–0.3) suits stationary demand with noise. Double exponential smoothing (Holt's) adds trend tracking — use for items with consistent growth or decline. Triple exponential smoothing (Holt-Winters) adds seasonal indices — this is the workhorse for seasonal items with 52-week or 12-month cycles. The alpha/beta/gamma parameters are critical: high alpha (>0.3) chases noise in volatile items; low alpha (<0.1) responds too slowly to regime changes. Optimize on holdout data, never on the same data used for fitting.
-
-**Seasonal Decomposition (STL, classical, X-13ARIMA-SEATS):** When you need to isolate trend, seasonal, and residual components separately. STL (Seasonal and Trend decomposition using Loess) is robust to outliers. Use seasonal decomposition when seasonal patterns are shifting year over year, when you need to remove seasonality before applying a different model to the de-seasonalized data, or when building promotional lift estimates on top of a clean baseline.
-
-**Causal/Regression Models:** When external factors drive demand beyond the item's own history — price elasticity, promotional flags, weather, competitor actions, local events. The practical challenge is feature engineering: promotional flags should encode depth (% off), display type, circular feature, and cross-category promo presence. Overfitting on sparse promo history is the single biggest pitfall. Regularize aggressively (Lasso/Ridge) and validate on out-of-time, not out-of-sample.
-
-**Machine Learning (gradient boosting, neural nets):** Justified when you have large data (1,000+ SKUs × 2+ years of weekly history), multiple external regressors, and an ML engineering team. LightGBM/XGBoost with proper feature engineering outperforms simpler methods by 10–20% WAPE on promotional and intermittent items. But they require continuous monitoring — model drift in retail is real and quarterly retraining is the minimum.
-
-### Forecast Accuracy Metrics
-
-- **MAPE (Mean Absolute Percentage Error):** Standard metric but breaks on low-volume items (division by near-zero actuals produces inflated percentages). Use only for items averaging 50+ units/week.
-- **Weighted MAPE (WMAPE):** Sum of absolute errors divided by sum of actuals. Prevents low-volume items from dominating the metric. This is the metric finance cares about because it reflects dollars.
-- **Bias:** Average signed error. Positive bias = forecast systematically too high (overstock risk). Negative bias = systematically too low (stockout risk). Bias < ±5% is healthy. Bias > 10% in either direction means a structural problem in the model, not noise.
-- **Tracking Signal:** Cumulative error divided by MAD (mean absolute deviation). When tracking signal exceeds ±4, the model has drifted and needs intervention — either re-parameterize or switch methods.
-
-### Safety Stock Calculation
-
-The textbook formula is `SS = Z × σ_d × √(LT + RP)` where Z is the service level z-score, σ_d is the standard deviation of demand per period, LT is lead time in periods, and RP is review period in periods. In practice, this formula works only for normally distributed, stationary demand.
-
-**Service Level Targets:** 95% service level (Z=1.65) is standard for A-items. 99% (Z=2.33) for critical/A+ items where stockout cost dwarfs holding cost. 90% (Z=1.28) is acceptable for C-items. Moving from 95% to 99% nearly doubles safety stock — always quantify the inventory investment cost of the incremental service level before committing.
-
-**Lead Time Variability:** When vendor lead times are uncertain, use `SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²)` — this captures both demand variability and lead time variability. Vendors with coefficient of variation (CV) on lead time > 0.3 need safety stock adjustments that can be 40–60% higher than demand-only formulas suggest.
-
-**Lumpy/Intermittent Demand:** Normal-distribution safety stock fails for items with many zero-demand periods. Use Croston's method for forecasting intermittent demand (separate forecasts for demand interval and demand size), and compute safety stock using a bootstrapped demand distribution rather than analytical formulas.
-
-**New Products:** No demand history means no σ_d. Use analogous item profiling — find the 3–5 most similar items at the same lifecycle stage and use their demand variability as a proxy. Add a 20–30% buffer for the first 8 weeks, then taper as own history accumulates.
-
-### Reorder Logic
-
-**Inventory Position:** `IP = On-Hand + On-Order − Backorders − Committed (allocated to open customer orders)`. Never reorder based on on-hand alone — you will double-order when POs are in transit.
-
-**Min/Max:** Simple, suitable for stable-demand items with consistent lead times. Min = average demand during lead time + safety stock. Max = Min + EOQ. When IP drops to Min, order up to Max. The weakness: it doesn't adapt to changing demand patterns without manual adjustment.
-
-**Reorder Point / EOQ:** ROP = average demand during lead time + safety stock. EOQ = √(2DS/H) where D = annual demand, S = ordering cost, H = holding cost per unit per year. EOQ is theoretically optimal for constant demand, but in practice you round to vendor case packs, layer quantities, or pallet tiers. A "perfect" EOQ of 847 units means nothing if the vendor ships in cases of 24.
-
-**Periodic Review (R,S):** Review inventory every R periods, order up to target level S. Better when you consolidate orders to a vendor on fixed days (e.g., Tuesday orders for Thursday pickup). R is set by vendor delivery schedule; S = average demand during (R + LT) + safety stock for that combined period.
-
-**Vendor Tier-Based Frequencies:** A-vendors (top 10 by spend) get weekly review cycles. B-vendors (next 20) get bi-weekly. C-vendors (remaining) get monthly. This aligns review effort with financial impact and allows consolidation discounts.
-
-### Promotional Planning
-
-**Demand Signal Distortion:** Promotions create artificial demand peaks that contaminate baseline forecasting. Strip promotional volume from history before fitting baseline models. Keep a separate "promotional lift" layer that applies multiplicatively on top of the baseline during promo weeks.
-
-**Lift Estimation Methods:** (1) Year-over-year comparison of promoted vs. non-promoted periods for the same item. (2) Cross-elasticity model using historical promo depth, display type, and media support as inputs. (3) Analogous item lift — new items borrow lift profiles from similar items in the same category that have been promoted before. Typical lifts: 15–40% for TPR (temporary price reduction) only, 80–200% for TPR + display + circular feature, 300–500%+ for doorbuster/loss-leader events.
-
-**Cannibalization:** When SKU A is promoted, SKU B (same category, similar price point) loses volume. Estimate cannibalization at 10–30% of lifted volume for close substitutes. Ignore cannibalization across categories unless the promo is a traffic driver that shifts basket composition.
-
-**Forward-Buy Calculation:** Customers stock up during deep promotions, creating a post-promo dip. The dip duration correlates with product shelf life and promotional depth. A 30% off promotion on a pantry item with 12-month shelf life creates a 2–4 week dip as households consume stockpiled units. A 15% off promotion on a perishable produces almost no dip.
-
-**Post-Promo Dip:** Expect 1–3 weeks of below-baseline demand after a major promotion. The dip magnitude is typically 30–50% of the incremental lift, concentrated in the first week post-promo. Failing to forecast the dip leads to excess inventory and markdowns.
-
-### ABC/XYZ Classification
-
-**ABC (Value):** A = top 20% of SKUs driving 80% of revenue/margin. B = next 30% driving 15%. C = bottom 50% driving 5%. Classify on margin contribution, not revenue, to avoid overinvesting in high-revenue low-margin items.
-
-**XYZ (Predictability):** X = CV of demand < 0.5 (highly predictable). Y = CV 0.5–1.0 (moderately predictable). Z = CV > 1.0 (erratic/lumpy). Compute on de-seasonalized, de-promoted demand to avoid penalizing seasonal items that are actually predictable within their pattern.
-
-**Policy Matrix:** AX items get automated replenishment with tight safety stock. AZ items need human review every cycle — they're high-value but erratic. CX items get automated replenishment with generous review periods. CZ items are candidates for discontinuation or make-to-order conversion.
-
-### Seasonal Transition Management
-
-**Buy Timing:** Seasonal buys (e.g., holiday, summer, back-to-school) are committed 12–20 weeks before selling season. Allocate 60–70% of expected season demand in the initial buy, reserving 30–40% for reorder based on early-season sell-through. This "open-to-buy" reserve is your hedge against forecast error.
-
-**Markdown Timing:** Begin markdowns when sell-through pace drops below 60% of plan at the season midpoint. Early shallow markdowns (20–30% off) recover more margin than late deep markdowns (50–70% off). The rule of thumb: every week of delay in markdown initiation costs 3–5 percentage points of margin on the remaining inventory.
-
-**Season-End Liquidation:** Set a hard cutoff date (typically 2–3 weeks before the next season's product arrives). Everything remaining at cutoff goes to outlet, liquidator, or donation. Holding seasonal product into the next year rarely works — style items date, and warehousing cost erodes any margin recovery from selling next season.
-
-## Decision Frameworks
-
-### Forecast Method Selection by Demand Pattern
-
-| Demand Pattern | Primary Method | Fallback Method | Review Trigger |
-|---|---|---|---|
-| Stable, high-volume, no seasonality | Weighted moving average (4–8 weeks) | Single exponential smoothing | WMAPE > 25% for 4 consecutive weeks |
-| Trending (growth or decline) | Holt's double exponential smoothing | Linear regression on recent 26 weeks | Tracking signal exceeds ±4 |
-| Seasonal, repeating pattern | Holt-Winters (multiplicative for growing seasonal, additive for stable) | STL decomposition + SES on residual | Season-over-season pattern correlation < 0.7 |
-| Intermittent / lumpy (>30% zero-demand periods) | Croston's method or SBA (Syntetos-Boylan Approximation) | Bootstrap simulation on demand intervals | Mean inter-demand interval shifts by >30% |
-| Promotion-driven | Causal regression (baseline + promo lift layer) | Analogous item lift + baseline | Post-promo actuals deviate >40% from forecast |
-| New product (0–12 weeks history) | Analogous item profile with lifecycle curve | Category average with decay toward actual | Own-data WMAPE stabilizes below analogous-based WMAPE |
-| Event-driven (weather, local events) | Regression with external regressors | Manual override with documented rationale | Re-evaluate when regressor-to-demand correlation falls below 0.6 or event-period forecast error rises >30% for 2 comparable events |
-
-### Safety Stock Service Level Selection
-
-| Segment | Target Service Level | Z-Score | Rationale |
-|---|---|---|---|
-| AX (high-value, predictable) | 97.5% | 1.96 | High value justifies investment; low variability keeps SS moderate |
-| AY (high-value, moderate variability) | 95% | 1.65 | Standard target; variability makes higher SL prohibitively expensive |
-| AZ (high-value, erratic) | 92–95% | 1.41–1.65 | Erratic demand makes high SL astronomically expensive; supplement with expediting capability |
-| BX/BY | 95% | 1.65 | Standard target |
-| BZ | 90% | 1.28 | Accept some stockout risk on mid-tier erratic items |
-| CX/CY | 90–92% | 1.28–1.41 | Low value doesn't justify high SS investment |
-| CZ | 85% | 1.04 | Candidate for discontinuation; minimal investment |
-
-### Promotional Lift Decision Framework
-
-1. **Is there historical lift data for this SKU-promo type combination?** → Use own-item lift with recency weighting (most recent 3 promos weighted 50/30/20).
-2. **No own-item data but same category has been promoted?** → Use analogous item lift adjusted for price point and brand tier.
-3. **Brand-new category or promo type?** → Use conservative category-average lift discounted 20%. Build in a wider safety stock buffer for the promo period.
-4. **Cross-promoted with another category?** → Model the traffic driver separately from the cross-promo beneficiary. Apply cross-elasticity coefficient if available; default 0.15 lift for cross-category halo.
-5. **Always model the post-promo dip.** Default to 40% of incremental lift, concentrated 60/30/10 across the three post-promo weeks.
-
-### Markdown Timing Decision
-
-| Sell-Through at Season Midpoint | Action | Expected Margin Recovery |
-|---|---|---|
-| ≥ 80% of plan | Hold price. Reorder cautiously if weeks of supply < 3. | Full margin |
-| 60–79% of plan | Take 20–25% markdown. No reorder. | 70–80% of original margin |
-| 40–59% of plan | Take 30–40% markdown immediately. Cancel any open POs. | 50–65% of original margin |
-| < 40% of plan | Take 50%+ markdown. Explore liquidation channels. Flag buying error for post-mortem. | 30–45% of original margin |
-
-### Slow-Mover Kill Decision
-
-Evaluate quarterly. Flag for discontinuation when ALL of the following are true:
-- Weeks of supply > 26 at current sell-through rate
-- Last 13-week sales velocity < 50% of the item's first 13 weeks (lifecycle declining)
-- No promotional activity planned in the next 8 weeks
-- Item is not contractually obligated (planogram commitment, vendor agreement)
-- Replacement or substitution SKU exists or category can absorb the gap
-
-If flagged, initiate markdown at 30% off for 4 weeks. If still not moving, escalate to 50% off or liquidation. Set a hard exit date 8 weeks from first markdown. Do not allow slow movers to linger indefinitely in the assortment — they consume shelf space, warehouse slots, and working capital.
-
-## Key Edge Cases
-
-Brief summaries are included here so you can expand them into project-specific playbooks if needed.
-
-1. **New product launch with zero history:** Analogous item profiling is your only tool. Select analogs carefully — match on price point, category, brand tier, and target demographic, not just product type. Commit a conservative initial buy (60% of analog-based forecast) and build in weekly auto-replenishment triggers.
-
-2. **Viral social media spike:** Demand jumps 500–2,000% with no warning. Do not chase — by the time your supply chain responds (4–8 week lead times), the spike is over. Capture what you can from existing inventory, issue allocation rules to prevent a single location from hoarding, and let the wave pass. Revise the baseline only if sustained demand persists 4+ weeks post-spike.
-
-3. **Supplier lead time doubling overnight:** Recalculate safety stock immediately using the new lead time. If SS doubles, you likely cannot fill the gap from current inventory. Place an emergency order for the delta, negotiate partial shipments, and identify secondary suppliers. Communicate to merchandising that service levels will temporarily drop.
-
-4. **Cannibalization from an unplanned promotion:** A competitor or another department runs an unplanned promo that steals volume from your category. Your forecast will over-project. Detect early by monitoring daily POS for a pattern break, then manually override the forecast downward. Defer incoming orders if possible.
-
-5. **Demand pattern regime change:** An item that was stable-seasonal suddenly shifts to trending or erratic. Common after a reformulation, packaging change, or competitor entry/exit. The old model will fail silently. Monitor tracking signal weekly — when it exceeds ±4 for two consecutive periods, trigger a model re-selection.
-
-6. **Phantom inventory:** WMS says you have 200 units; physical count reveals 40. Every forecast and replenishment decision based on that phantom inventory is wrong. Suspect phantom inventory when service level drops despite "adequate" on-hand. Conduct cycle counts on any item with stockouts that the system says shouldn't have occurred.
-
-7. **Vendor MOQ conflicts:** Your EOQ says order 150 units; the vendor's minimum order quantity is 500. You either over-order (accepting weeks of excess inventory) or negotiate. Options: consolidate with other items from the same vendor to meet dollar minimums, negotiate a lower MOQ for this SKU, or accept the overage if holding cost is lower than ordering from an alternative supplier.
-
-8. **Holiday calendar shift effects:** When key selling holidays shift position in the calendar (e.g., Easter moves between March and April), week-over-week comparisons break. Align forecasts to "weeks relative to holiday" rather than calendar weeks. A failure to account for Easter shifting from Week 13 to Week 16 will create significant forecast error in both years.
-
-## Communication Patterns
-
-### Tone Calibration
-
-- **Vendor routine reorder:** Transactional, brief, PO-reference-driven. "PO #XXXX for delivery week of MM/DD per our agreed schedule."
-- **Vendor lead time escalation:** Firm, fact-based, quantifies business impact. "Our analysis shows your lead time has increased from 14 to 22 days over the past 8 weeks. This has resulted in X stockout events. We need a corrective plan by [date]."
-- **Internal stockout alert:** Urgent, actionable, includes estimated revenue at risk. Lead with the customer impact, not the inventory metric. "SKU X will stock out at 12 locations by Thursday. Estimated lost sales: $XX,000. Recommended action: [expedite/reallocate/substitute]."
-- **Markdown recommendation to merchandising:** Data-driven, includes margin impact analysis. Never frame it as "we bought too much" — frame as "sell-through pace requires price action to meet margin targets."
-- **Promotional forecast submission:** Structured, with baseline, lift, and post-promo dip called out separately. Include assumptions and confidence range. "Baseline: 500 units/week. Promotional lift estimate: 180% (900 incremental). Post-promo dip: −35% for 2 weeks. Confidence: ±25%."
-- **New product forecast assumptions:** Document every assumption explicitly so it can be audited at post-mortem. "Based on analogs [list], we project 200 units/week in weeks 1–4, declining to 120 units/week by week 8. Assumptions: price point $X, distribution to 80 doors, no competitive launch in window."
-
-Brief templates appear above. Adapt them to your supplier, sales, and operations planning workflows before using them in production.
-
-## Escalation Protocols
-
-### Automatic Escalation Triggers
-
-| Trigger | Action | Timeline |
-|---|---|---|
-| Projected stockout on A-item within 7 days | Alert demand planning manager + category merchant | Within 4 hours |
-| Vendor confirms lead time increase > 25% | Notify supply chain director; recalculate all open POs | Within 1 business day |
-| Promotional forecast miss > 40% (over or under) | Post-promo debrief with merchandising and vendor | Within 1 week of promo end |
-| Excess inventory > 26 weeks of supply on any A/B item | Markdown recommendation to merchandising VP | Within 1 week of detection |
-| Forecast bias exceeds ±10% for 4 consecutive weeks | Model review and re-parameterization | Within 2 weeks |
-| New product sell-through < 40% of plan after 4 weeks | Assortment review with merchandising | Within 1 week |
-| Service level drops below 90% for any category | Root cause analysis and corrective plan | Within 48 hours |
-
-### Escalation Chain
-
-Level 1 (Demand Planner) → Level 2 (Planning Manager, 24 hours) → Level 3 (Director of Supply Chain Planning, 48 hours) → Level 4 (VP Supply Chain, 72+ hours or any A-item stockout at enterprise customer)
-
-## Performance Indicators
-
-Track weekly and trend monthly:
-
-| Metric | Target | Red Flag |
-|---|---|---|
-| WMAPE (weighted mean absolute percentage error) | < 25% | > 35% |
-| Forecast bias | ±5% | > ±10% for 4+ weeks |
-| In-stock rate (A-items) | > 97% | < 94% |
-| In-stock rate (all items) | > 95% | < 92% |
-| Weeks of supply (aggregate) | 4–8 weeks | > 12 or < 3 |
-| Excess inventory (>26 weeks supply) | < 5% of SKUs | > 10% of SKUs |
-| Dead stock (zero sales, 13+ weeks) | < 2% of SKUs | > 5% of SKUs |
-| Purchase order fill rate from vendors | > 95% | < 90% |
-| Promotional forecast accuracy (WMAPE) | < 35% | > 50% |
-
-## Additional Resources
-
-- Pair this skill with your SKU segmentation model, service-level policy, and planner override audit log.
-- Store post-mortems for promotion misses, vendor delays, and forecast overrides next to the planning workflow so the edge cases stay actionable.