Seven things to write down before anyone codes your EA

21 November 2026, 18:35
Felicien Badou Diouf
0
4

Most "the EA doesn't trade like me" complaints aren't coding bugs. The rules were never fully written down, so the coder (human or AI) had to guess.

Here are the seven gaps I see most often, and the sentence that closes each one.

1. When does a signal count?
"EMA 20 crosses above EMA 50" can mean on the live tick or on the closed bar. They give different trades.
Write: "Check signals on the close of each H1 bar only."

2. Where exactly is the stop?
"Stop below the swing low" needs a definition of a swing low.
Write: "Stop 1.5 × ATR(14) below entry" or "Stop below the lowest low of the last 10 bars."

3. How is size decided?
Fixed lots and risk-percent sizing behave very differently after a losing run.
Write: "Risk 0.5% of balance per trade, sized from the stop distance."

4. How many positions at once?
Write: "Only one position per symbol. Ignore new signals while a trade is open."

5. When does it not trade?
Write: "Trade 07:00–17:00 server time only. No new trades on Friday after 15:00."

6. What stops it for the day?
If you're on a prop account, this is the rule that keeps the challenge alive.
Write: "If the day's closed + open loss reaches 3% of starting balance, close everything and stop until the next day."

7. What if the spread is wide?
Write: "Skip entries when the spread is above 25 points."

Put those seven sentences together and you have a spec any developer can build without guessing. It also takes the back-and-forth out of a freelance job.

It's also exactly the input our AI EA Builder at BoltIQ is designed for. You paste the seven sentences, it writes the MQL5, compiles it in MetaEditor and gives you the source. Change a sentence and regenerate. The first drafts are free: try the AI EA Builder.

Whatever builds it, run it in the Strategy Tester on real ticks before it goes near a live account. A backtest is research, not a promise of profit.