gd-onhand-ops

Ops Morning Briefing Skill

What This Skill Does

Ops Morning Briefing is a daily read-only Skill that answers one question for the ops manager every weekday morning: what do I need to fix today on the floor and in the ledger?

It watches for two fast-moving operational signals: units stuck in transfer between Locations (physical TOs that haven't been received) and virtual transfer drafts queued up by the rebalance Skill that haven't been acted on. Both are situations where the ledger and the operation can drift apart if ignored.

This Skill does not draft transactions. Operational follow-through (transfers, adjustments) is handled by gd-safety-stock and gd-rebalance.

Scope note: Lot-level aging signals — stuck Reserved lots, cross-Channel stranded lots, Unsellable stale lots, aged inventory cohorts, dead stock, and turnover — moved to the weekly gd-aging-analysis Skill, which is their proper home and includes the FIFO two-transfer swap recommendation logic those findings need. If the user asks about any of those, route them to gd-aging-analysis.

Before You Start

1. Read the shared launch configuration: ../Configuration — Shared.md — schedule, delivery, output shape, Location classification table (Warehouse vs Retail Store), Data Source contract (Section 16).
2. Read this Skill's configuration: ./Configuration - Ops Morning Briefing.md.
3. Read the SOP: ./SOP - Ops Morning Briefing.md.
4. Apply the Brand Guide: ../🖼️ Brand Guidelines.pdf.
5. Resolve data source per the Data Source section below.

Data Source

This Skill describes the business entities each routine needs. The concrete mapping — which MCP tool, verified query, or CSV column populates each entity — lives in ../MCP Tool Catalog.md. When the GoodDay MCP renames a tool or publishes a new verified query, only the catalog changes; this Skill does not.

Session context comes from the connected MCP's standard surface; filter all results to Warehouse-classified Locations.

Entities this Skill needs — look each one up in the catalog:

Routine	Entity needed
1 — Stale Transfers	Physical Transfer Orders past their ETA without complete destination receipt, with origin and destination Location IDs, days past ETA, and lifecycle status
1 — Draft-receipt sub-flag	For each Routine 1 candidate, the existence of a draft receipt at the destination
1 — Drill-in detail	Real-time single-Transfer detail when an operator drills in
2 — Virtual Transfer Drafts	Outstanding draft Transfer Orders where origin Location equals destination Location (virtual / same-Location rebalance pattern)
Both routines — $ exposure	Lot-grain inventory valuation joined to flagged TO lines by SKU + Location
Cross-tool sanity check	None required — Routine 1 + Routine 2 are self-consistent over check_transfers

Output delivery and drill links per ../Configuration — Shared.md and per-row deep_link.

Catalog bindings for this Skill are on live production tools — transfers and lot-grain inventory valuation. If any catalog binding returns VALIDATION_ERROR: not_found, follow ../Configuration — Shared.md Section 12b.

Workflow

Routine 1: Stale Transfers          → Physical TOs in transit >7d, draft-receipt flag if present
Routine 2: Virtual Transfer Drafts  → Outstanding drafts from gd-rebalance
Scorecard: ops-briefing-scorecard   → Severity-scored roll-up of both

Routine 1 — Stale Transfers

Identify physical Transfer Orders fulfilled at origin beyond the Stale transfer threshold from ./Configuration - Ops Morning Briefing.md Section 2 (Stale Transfers) that have not been fully received at destination. For each, check whether a draft receipt exists at the destination — flag prominently when it does (most common, easiest fix).

Routine 2 — Virtual Transfer Drafts

Read outstanding draft Transfer Orders created by gd-rebalance. Report new drafts since the previous run; otherwise report "no change since yesterday" with current queue depth.

Scorecard — ops-briefing-scorecard

Read outputs of Routines 1–2. Do not re-detect. Apply the severity rules defined in ./Configuration - Ops Morning Briefing.md Section 1 (Severity thresholds). Compose the headline ("Today's punch list"), top-10 punch list, and tail summary per the shared Output shape (../Configuration — Shared.md Section 7).

Output

Follow the output shape from the shared Configuration:

• Headline — severity badge + units at risk + $ exposure
• Scorecard punch list — top-10 across both routines
• Tail line — +N more lines totaling $X if more than 10
• Detail by routine — top-10 + tail per routine
• Persistent issues — items on 3 of last 5 runs
• Temporarily ignored — visibility section

Render against the GoodDay Brand Guide. Post to the configured Slack channel for scheduled runs.

Caveats to Always Include

1. The Skill flags but does not act. Routes the user to gd-safety-stock and gd-rebalance for operational follow-through.
2. Warehouse Locations only. Retail Stores excluded via the shared Location classification table.
3. Lot-level aging signals live elsewhere. Route requests about stuck Reserved lots, cross-Channel stranded lots, Unsellable stale lots, dead stock, or turnover to gd-aging-analysis.

Edge Cases

• Zero findings in a routine: Report "None found — this is what healthy looks like" rather than omitting the section.
• Persistent issue without movement: Surface in the scorecard headline as a callout — the daily fix isn't holding.
• Draft receipt count mismatch: If multiple drafts exist for the same Transfer Order, list them all.
• User asks about stuck lots / aged inventory / dead stock / turnover: Politely route to gd-aging-analysis (weekly, Monday) — that's the proper home for those signals.