Sales Season Order Generation

Problem

Order generation often breaks down on inconsistent field definitions: order ID, line items, quantities, amounts, customer, and dates may arrive as scattered messages or table fragments. If a model writes the result immediately, it can miss required fields or bind values to the wrong keys. This skill frames the task as collecting fields step by step and writing them into JSON, which fits sales-season workflows where the order structure is relatively fixed.

How It Works

The skill does not assume a complete order is available upfront. It uses a field-by-field flow:
- Prompt for missing fields: it asks for absent values in stages instead of requiring one long form.
- Accumulate structure: each response is mapped into an order object, making line items, customer details, and amount fields easier to assemble.
- Emit JSON: the final output is a structured document that downstream scripts, tables, or manual review can consume.

Boundaries

This is closer to an order draft or field-intake helper than a full order management system. The provided documentation does not confirm ERP, CRM, payment, or inventory integration, nor does it define field enums, validation rules, or reuse of historical orders. Before use, define the expected JSON schema and confirm key names, amount units, and required fields; otherwise the result may need manual correction before entering billing or settlement workflows.