Fill the fields above, then generate the brief.
Why this matters before MT5 development
Many strategy descriptions mix objective rules with visual judgment. A developer cannot reliably code phrases such as “strong candle”, “good support”, “clean breakout” or “enter when momentum looks right” unless each one is converted into measurable conditions. A structured brief makes those ambiguities visible early.
What a complete EA specification should cover
- Signal definition: exact indicator, price-action or structure conditions and the order in which they must occur.
- State: whether a setup remains valid for one candle, several bars, until invalidated, or until a session ends.
- Execution: market versus pending orders, maximum spread, slippage behavior and retry rules.
- Risk: fixed volume or percentage risk, total portfolio exposure and daily loss limits.
- Management: partial closes, break-even, trailing stops, pyramiding and opposite-signal behavior.
- Failure behavior: what the EA does when the broker rejects an order, data is missing or the terminal reconnects.
- Validation: data period, metrics and acceptance criteria for backtest and forward test.
Related resources
Custom MT5 EA DevelopmentArchitecture, execution, testing and delivery considerations.
MT5 Position Size CalculatorCheck risk-based sizing assumptions.
XAUUSD Bot GuideGold-specific execution and validation.
Discuss your generated briefUse the output as the starting point for a scoped development conversation.
This tool helps document software requirements. It does not evaluate whether a trading strategy is profitable and does not provide financial advice.