Design the order lifecycle — order state machine, fulfillment workflow, returns/RMA, refunds, cancellations, and order events/webhooks. Platform-agnostic state and event modeling. Triggers: designing order states, modeling returns/refunds, defining order events.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
An order is a long-lived state machine touched by payments, inventory, shipping, and support. Model its states, transitions, and events explicitly so nothing silently gets stuck — independent of platform.
Note: This skill may create or modify files in your project (a state-machine spec). It will ask before writing.
Gather: fulfillment model (single vs split/partial shipments), payment capture timing (auth-then-capture vs immediate), returns policy, and goal (design the full lifecycle, define the state machine, or model returns/refunds).
| Mode | Trigger | Output |
|---|---|---|
| Design | design | End-to-end lifecycle + events |
| States | states | Formal state machine: states, transitions, guards |
| Returns | returns | RMA + refund flow and states |
Separate order status from payment status and fulfillment status — collapsing them into one field is the most common modeling mistake.
| Dimension | States |
|---|---|
| Order | pending → confirmed → in_progress → completed / cancelled |
| Payment | pending → authorized → paid → partially_refunded → refunded / failed |
| Fulfillment | unfulfilled → partially_fulfilled → fulfilled → returned |
Each transition has a guard (e.g. cannot fulfill before payment authorized) and emits an event.
For the full transition table, guards, and partial-shipment handling, see references/order-state-machine.md.
Every transition emits a durable, ordered event: order.created, order.paid, order.fulfilled, order.cancelled, order.refunded, return.requested, return.received.
payments-architecture for the reliability pattern).Flow: return.requested → approved → label_sent → in_transit → received → inspected → refunded/rejected.
| Concern | Rule |
|---|---|
| Restock | Only on received + inspected pass, back to available |
| Refund | Full / partial / store-credit; never exceed captured amount |
| Window | Enforce return-window guard at request time |
| Partial | Per line-item, not whole-order, for split fulfillment |
| Request | Output |
|---|---|
| Design | Lifecycle diagram + event catalog |
| States | State/transition/guard table (the spec) |
| Returns | RMA flow + refund rules |
A lifecycle design is COMPLETE when order/payment/fulfillment statuses are independent, every transition has a guard and an event, and refunds/restocks are gated on inspection.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.
The English summary is being prepared. Showing the original description.
Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.
The English summary is being prepared. Showing the original description.
Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.
The English summary is being prepared. Showing the original description.
Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.
The English summary is being prepared. Showing the original description.
Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.
The English summary is being prepared. Showing the original description.
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.
The English summary is being prepared. Showing the original description.