order-lifecycle

Enforce a five-step POS ticket lifecycle in legacy INI integrations.

Updated Mar 14, 2026

Search Tags:#workflow #concurrency #transactions #scheduling #idempotency #order #pos-integration

Ready to run

npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill order-lifecycle-novatech2210-cmd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: order-lifecycle
Source: https://github.com/novatech2210-cmd/ImidusApp/tree/main/.gemini/agents/order-lifecycle
Command: npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill order-lifecycle-novatech2210-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open and reconcile POS tickets without desynchronization, duplicates, or failed payments by enforcing the canonical 5-step lifecycle in legacy INI POS integrations.

Core Features & Use Cases

Contract-driven workflow for creating open tickets, adding line items, recording payments, finalizing totals, and moving items to detail lines within guarded transactions.
Idempotency and concurrency safeguards to prevent duplicate orders and race conditions across distributed services.
Support for scheduled orders and online bridges with clear ownership of Step 5.

Quick Start

Implement the lifecycle by mirroring the five steps inside a single transaction, ensuring idempotency, concurrency guards, and correct handoff to the POS for Step 5.

Frequently Asked Questions about order-lifecycle

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

FAQPage Schema

How do I prevent duplicate POS orders and race conditions in a legacy integration?▼

POS ticket reconciliation prevents desynchronization by finalizing totals and moving items to detail lines within guarded transactions. It ensures safe completion semantics across distributed services before moving items to tblSalesDetail.

How do I handle scheduled orders within a POS ticket lifecycle?▼

Scheduled orders use overlays to apply the five-step lifecycle, supporting online bridges while ensuring clear ownership of Step 5. This maintains safe completion semantics for future-dated transactions.

Can I use this 5-step workflow for processing payments across distributed services?▼

Yes, this 5-step workflow supports payment recording by applying idempotency guarantees inside transactions. It ensures safe completion semantics across distributed services interacting with tblPayment.

What is the best way to ensure safe completion semantics for POS transactions?▼

The best way to ensure safe completion semantics is enforcing a contract-driven 5-step workflow. This automates lifecycle stages across tblSales and tblPendingOrders within guarded transactions to prevent desynchronization.