Pre-Trade Quality Gate

Pain point

Forced trades often happen when the trader skips their own criteria and trades "because something is moving."

Triggers

• Any new trade-entry attempt

Conditions

• Skip checklist only for pre-defined "playbook" templates (optional)
• Optional: require checklist only after the first 2 trades (to reduce friction early)

Actions

• Ask 5 yes/no questions; if any are "no," recommend skipping
• If proceeding, require selecting a setup tag (ORB, pullback, mean reversion, etc.)
• Create a journal stub automatically

Parameters (defaults)

• questions:
• "Is this an A/B setup from my playbook?"
• "Is my invalidation level defined?"
• "Is size derived from risk (not emotion)?"
• "Is liquidity/spread acceptable?"
• "Am I trading in my allowed time window?"
• requireSetupTag: true

Examples

• If you can't define invalidation, the recipe recommends "no trade" and starts a watch-only alert.
• If spread is above limit, it blocks market orders and suggests limit-entry only.