stock-movement-audit

Records immutable inventory movement entries and updates running stock levels in gbrain.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill stock-movement-audit-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stock-movement-audit
Source: https://github.com/tapway/shogun-os/tree/main/skills/procurement/stock-movement-audit
Command: npx skills add https://github.com/tapway/shogun-os --skill stock-movement-audit-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inventory teams lose track of goods received, issued, adjusted, or damaged when movements are logged informally, making shrinkage audits and stock reconciliation unreliable. ## Core Features & Use Cases - Immutable Movement Logging: Appends tamper-evident entries to procurement/stock-movements/ in gbrain with SKU, movement type, quantity, reference ID, location, and actor. - Atomic Stock Updates: Calls proc_update_stock after each movement so the item master page always reflects the current running total. - Damage Monitoring: Flags SKUs whose cumulative damage exceeds 2% of stock within 30 days. - Use Case: When a shipment arrives against PO-2026-0312, the agent verifies each SKU, logs a receive movement per line item, and updates stock from 5 to 205 units with a traceable movement ID. ## Quick Start Ask the procurement agent to record a stock receipt for your purchase order number with the SKUs, quantities, and receiving location.

Frequently Asked Questions about stock-movement-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record a goods receipt against a purchase order?

Provide the PO number, SKU list with quantities, and receiving location. The skill verifies each SKU with proc_get_item, logs a receive movement via proc_record_stock_movement, then updates the running stock level with proc_update_stock.

How to audit recent inventory movements in gbrain?

Query the procurement/stock-movements/ pages for the desired date range. Results are formatted as a table with timestamp, SKU, movement type, quantity, reference ID, location, and actor, with damage and adjustment entries highlighted.

Can stock go negative when issuing inventory?

The skill checks current stock via proc_get_item before issuing and rejects the movement if it would go negative. The proc_update_stock API itself does not block negative values, so the pre-check is required.

Why must every stock movement have a reference ID?

A PO number or ticket reference ensures traceability and prevents duplicate entries, such as double-counted receipts for the same purchase order. Movements with a blank reference are not logged.

When should I not use stock movement logging?

Do not use it to create or edit SKU master records; that belongs to the inventory-item-management skill. This skill only appends movement entries and adjusts running stock levels.