Back to Cookbook

Order Ticket Sanity Checker

Catch order-type mistakes before the market does

A pre-submit check for market, limit, and stop orders that explains what the order actually does and where users commonly misunderstand it.

CommunitySubmitted by CommunityPersonal2 min

PROMPT

Create a skill called "Order Ticket Sanity Checker". Before I place a trade, let me paste the order details and tell me: - what the order actually does in plain English, - what can go wrong, - where I may be misunderstanding it, - and whether a different order type better matches my intent.

How It Works

This recipe targets confusion about order types and execution expectations.

Triggers

  • You are about to place an order and want a second set of eyes
  • You are not sure whether to use market, limit, or stop
  • You fear a bad fill or unintended execution

Inputs

  • Buy or sell
  • Order type
  • Limit or stop price
  • Ticker
  • Time in force

Outputs

  • Plain-English explanation of what the order will do
  • Common misunderstanding warning
  • Execution expectation in best and worst case
  • Safer alternative if the order type conflicts with the stated intent

Steps / Actions

  1. Translate the ticket into plain language.
  2. Explain best-case and worst-case behavior.
  3. Warn if the ticket conflicts with the stated intention.
  4. Summarize before submission.

Failure Modes

  • User thinks a limit order guarantees execution
  • User thinks a stop limit guarantees downside protection
Tags:#orders#execution#trading#education