vertical-logistics

Provide logistics domain vocabulary, rules, and entity modeling for product specifications.

75|13|Updated Apr 5, 2026

Search Tags:#architecture #product management #logistics #supply chain #domain knowledge

Ready to run

npx skills add https://github.com/avelikiy/great_cto --skill vertical-logistics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vertical-logistics
Source: https://github.com/avelikiy/great_cto/tree/main/skills/vertical-logistics
Command: npx skills add https://github.com/avelikiy/great_cto --skill vertical-logistics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides domain knowledge for the logistics & supply chain vertical, ensuring architects and product managers avoid naive specifications and build more robust systems.

Core Features & Use Cases

Domain Vocabulary: Covers terms like TMS vs WMS, multi-carrier rate shopping, dimensional weight, BOL/ASN, lot/batch, reorder point, and more.
Non-Obvious Rules: Identifies key rules that incumbent systems follow, such as normalized tracking statuses, branded tracking, route optimization, and PO lifecycle management.
Entity Modeling: Defines the necessary entities for four products: shipment-tracking, warehouse-lite, route-optimization, and po-mgmt, with detailed specifications for each.
Use Case: When planning a logistics product, this Skill helps in specifying requirements for shipments, carriers, tracking, warehouses, inventory, and routes without underestimating complexity.

Quick Start

Apply the vertical-logistics skill when writing specifications for logistics-related features in your product documentation.

Frequently Asked Questions about vertical-logistics

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

FAQPage Schema

What domain vocabulary do I need for logistics and supply chain architecture?▼

Logistics and supply chain architecture requires understanding domain vocabulary like TMS vs WMS, multi-carrier rate shopping, dimensional weight, BOL/ASN, and lot/batch tracking to build robust systems. These terms define the core entities and rules for shipment, warehouse, and route products.

How do I model entities for a shipment tracking product?▼

To model entities for a shipment tracking product, you must define specifications for shipments, carriers, and normalized tracking statuses. This includes accounting for non-obvious rules like branded tracking and multi-carrier rate shopping to avoid naive specifications.

What are the non-obvious rules in warehouse-lite and route optimization systems?▼

Warehouse-lite and route optimization systems follow non-obvious incumbent rules such as reorder point calculations, lot/batch tracking, and route optimization constraints. Recognizing these rules prevents underestimating complexity when specifying inventory and routing entities.

Do I need prior logistics knowledge to specify supply chain product requirements?▼

Yes, specifying supply chain product requirements requires prior understanding of logistics concepts and practices. This domain knowledge is necessary to properly define vocabulary, entity modeling, and non-obvious rules for products like po-mgmt and shipment tracking.

What is the best way to plan a purchase order management product?▼

The best way to plan a purchase order management product is to define its PO lifecycle management rules and entity specifications upfront. This approach avoids naive specifications by addressing the specific domain vocabulary and non-obvious rules incumbent systems follow.

Why does logistics product planning often underestimate system complexity?▼

Logistics product planning often underestimates system complexity because architects miss non-obvious rules like normalized tracking statuses, dimensional weight, and PO lifecycle management. Without proper domain knowledge, specifications for warehouses, inventory, and routes lack robustness.